We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Mentioned in #255, OAuth 2.1 still support opaque token instead of JWT token, and opaque token is used widely in the real world application.
When decoding the user claims, instead of decoding the jwt token itself, it sends a Http request to the predefined userInfoUri attribute.
userInfoUri
I am not sure if we can consider both JWT and Opaque token introspection when we are introducing JWT authentication, #255 (comment)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Mentioned in #255, OAuth 2.1 still support opaque token instead of JWT token, and opaque token is used widely in the real world application.
When decoding the user claims, instead of decoding the jwt token itself, it sends a Http request to the predefined
userInfoUri
attribute.I am not sure if we can consider both JWT and Opaque token introspection when we are introducing JWT authentication, #255 (comment)
The text was updated successfully, but these errors were encountered: