Skip to content

Why Jwt is the only supported format for bearer tokens in Spring Security? #6231

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

Closed
ShanyouYu-Sean opened this issue Dec 5, 2018 · 1 comment

Comments

@ShanyouYu-Sean
Copy link

Summary

Seems Jwt is the only supported format for bearer tokens in Spring Security 5.1.+, why? Is there any plans implement a way to verify normal bearer token with userinfo endpoint or token introspect endpoint?

Actual Behavior

Cannot verify normal bearer token with userinfo endpoint or token introspect endpoint in Spring Security 5.1.+.

Expected Behavior

Provide a way to verify normal bearer token with userinfo endpoint or token introspect endpoint.

Version

Spring Security 5.1.2.RELEASE

@jgrandja
Copy link
Contributor

jgrandja commented Dec 5, 2018

@ShanyouYu-Sean Token Introspection (opaque token) support is planned for 5.2. You can track the progress in #5200.

@jgrandja jgrandja closed this as completed Dec 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants