Skip to content

Resource Server Multi-tenancy Sample Should Manage Its Own Jwt Decoder #7272

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
jzheaux opened this issue Aug 17, 2019 · 0 comments
Closed
Assignees
Labels
in: docs An issue in Documentation or samples type: enhancement A general enhancement
Milestone

Comments

@jzheaux
Copy link
Contributor

jzheaux commented Aug 17, 2019

Since oauth2resourceserver-multitenancy generates an AuthenticationManagerResolver, it should handle any of its own JwtDecoder or OpaqueTokenIntrospector instances.

As such, the application properties should be changed so as to not trigger Boot's autoconfiguration of these beans.

@jzheaux jzheaux added in: docs An issue in Documentation or samples type: enhancement A general enhancement labels Aug 17, 2019
@jzheaux jzheaux added this to the 5.2.0.RC1 milestone Aug 17, 2019
@jzheaux jzheaux self-assigned this Aug 17, 2019
@jzheaux jzheaux changed the title Resource Server Multi-tenancy Sample Should Not Generate Auto-generate JwtDecoder Resource Server Multi-tenancy Sample Should Manage Its Own Jwt Decoder Aug 17, 2019
kostya05983 pushed a commit to kostya05983/spring-security that referenced this issue Aug 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: docs An issue in Documentation or samples type: enhancement A general enhancement
Projects
None yet
Development

No branches or pull requests

1 participant