Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Very clear advice to user when using Opaque Access Token that this will not work anymore beacuse of breaking changes #131

Open
dniel opened this issue Sep 24, 2019 · 0 comments
Open

Very clear advice to user when using Opaque Access Token that this will not work anymore beacuse of breaking changes #131

dniel opened this issue Sep 24, 2019 · 0 comments
Assignees
@dniel
Labels
enhancement New feature or request

Comments

@dniel
Copy link
Owner

dniel commented Sep 24, 2019

In the new version its mandatory to use JWT Access Token to be able to verify that the access token is valid and has not expired. This can only be done if the Access Token is in JWT format.
Users that try to use the application with Opaque Access Token need to see a error message that very clearly describes this and what to do.
@dniel dniel added the enhancement New feature or request label Sep 24, 2019
@dniel dniel self-assigned this Sep 24, 2019
dniel added a commit that referenced this issue Sep 25, 2019
@dniel
#131 give much more clear error message on what to do when token is o…
a9b5bf6 
…paque.
dniel added a commit that referenced this issue Sep 25, 2019
@dniel
#131 change to return an invalid opaque token event instead of throwi…
919df1b 
…ng exception.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dniel dniel

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dniel