Panos Angelopoulos

Hi @Amertz08, I was trying to reproduce your issue but I couldn't. Steps which I followed: - Get a valid `refresh_token` - Sent 2, 4, and 10 concurrent post requests...

Thanks for your message @szicari-farmobile but still I cannot reproduce it even with 6 different panes plus using the `Broadcast Input to All Panes in Current Tab` approach. ``` curl...

Yes, @szicari-farmobile I mean panes, sorry for mention tabs. Even with 6 different panes, I cannot reproduce it. I realized that somehow there is a queue with the requests and...

Not really, all of them are returned correctly with a 200 status code. Even after running Django with a two-worker configuration as you suggested the issue is not showing up.

@szicari-farmobile regarding your concern you are right since I had configured the `REFRESH_TOKEN_EXPIRE_SECONDS` and `REFRESH_TOKEN_GRACE_PERIOD_SECONDS` to `60`, thus you can reuse the same refresh token. After comment out this configuration...

@szicari-farmobile Did you set `REFRESH_TOKEN_GRACE_PERIOD_SECONDS` and/or `REFRESH_TOKEN_EXPIRE_SECONDS` in the above requests ?

Then I'm not expecting two responses with `200` status. Anyone else who can reproduce the bug by using the method which @rtpg mentioned?

I did my research and came back to this topic, the reason that we are getting two valid requests (cc @szicari-farmobile ) when we are sending simultaneous requests is this...

I totally agree with the first part of your answer @rtpg, IMO adding a validator for a non-empty field doesn't make any sense. Regarding the second part, there is already...

A new [PR](https://github.com/jazzband/django-oauth-toolkit/pull/975) created