-
Notifications
You must be signed in to change notification settings - Fork 871
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: Getting 200 in refresh-token api for empty token #38
Comments
coderbdsust
changed the title
Getting 200 in refresh-api from empty token
Bug: Getting 200 in refresh-api from empty token
Jul 22, 2023
coderbdsust
changed the title
Bug: Getting 200 in refresh-api from empty token
Bug: Getting 200 in refresh-api for empty token
Jul 22, 2023
coderbdsust
changed the title
Bug: Getting 200 in refresh-api for empty token
Bug: Getting 200 in refresh-token api for empty token
Jul 22, 2023
can you share more context? |
Yes, I had the same issue. I now throw an AuthorizationException, catch it in the controller and set the HTTP response code to 401 for such use cases where the token is missing on the refresh API. Thanks @coderbdsust for sharing this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: