Skip to content

Add NimbusJwtDecoder#withIssuerLocation #10309

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
Closed
jzheaux opened this issue Sep 21, 2021 · 1 comment
Closed

Add NimbusJwtDecoder#withIssuerLocation #10309

jzheaux opened this issue Sep 21, 2021 · 1 comment
Assignees
@jzheaux
Labels
in: oauth2 An issue in OAuth2 modules (oauth2-core, oauth2-client, oauth2-resource-server, oauth2-jose) type: enhancement A general enhancement
Milestone
6.1.0-RC1

Comments

@jzheaux
Copy link
Contributor

jzheaux commented Sep 21, 2021 •
edited
Loading

Related #8885, #9904 (comment)

It would be nice to be able to provide an issuer location to NimbusJwtDecoder instead of a JWK Set URI.

It would allow the issuer discovery to share the same RestOperations/WebClient as the decode method does. Since the JWK Set is cached, this will save a call to the authorization server and also allow the RestOperations and WebClient used for issuer discovery to be configured.

This should be added for both NimbusJwtDecoder and NimbusReactiveJwtDecoder.
@jzheaux jzheaux added status: waiting-for-triage An issue we've not yet triaged type: enhancement A general enhancement labels Sep 21, 2021
@jzheaux jzheaux self-assigned this Sep 21, 2021
@jzheaux jzheaux mentioned this issue Sep 21, 2021
Merged
@sjohnr sjohnr added in: oauth2 An issue in OAuth2 modules (oauth2-core, oauth2-client, oauth2-resource-server, oauth2-jose) and removed status: waiting-for-triage An issue we've not yet triaged labels Sep 22, 2021
@jzheaux jzheaux mentioned this issue Jan 26, 2022
Closed
@sjohnr sjohnr mentioned this issue Apr 4, 2022
Open
@jzheaux jzheaux mentioned this issue May 9, 2022
Closed
@jgrandja jgrandja mentioned this issue May 26, 2022
Closed
@jgrandja
Copy link
Contributor

@jzheaux Please see this comment as a potential alternative to this issue. Any feedback would be greatly appreciated.

@jgrandja jgrandja added this to the 5.8.0-M2 milestone Jul 18, 2022
@wilkinsona wilkinsona mentioned this issue Jul 19, 2022
Closed
@jgrandja jgrandja mentioned this issue Jul 25, 2022
Closed
@rwinch rwinch modified the milestones: 5.8.0-M2, 5.8.0-M3 Aug 12, 2022
@sjohnr sjohnr modified the milestones: 5.8.0-M3, 5.8.0-RC1 Sep 16, 2022
@jzheaux jzheaux modified the milestones: 5.8.0-RC1, 6.0.x, 6.1.0-M1 Oct 5, 2022
@jgrandja jgrandja removed this from the 6.1.0-M1 milestone Dec 19, 2022
@jgrandja jgrandja self-assigned this Jan 12, 2023
@jgrandja jgrandja added this to the 6.1.0-M3 milestone Apr 3, 2023
@jgrandja jgrandja removed their assignment Apr 13, 2023
@heruan heruan mentioned this issue Feb 18, 2024
Closed
@alfespa17 alfespa17 mentioned this issue Mar 20, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jzheaux jzheaux

Labels
in: oauth2 An issue in OAuth2 modules (oauth2-core, oauth2-client, oauth2-resource-server, oauth2-jose) type: enhancement A general enhancement
Projects
None yet
Milestone
6.1.0-RC1
Development

No branches or pull requests
4 participants
@rwinch @jzheaux @sjohnr @jgrandja