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.

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

Support setting multiple issuers #4

Open
lcmgh opened this issue Jul 10, 2023 · 2 comments
Open

Support setting multiple issuers #4

lcmgh opened this issue Jul 10, 2023 · 2 comments

Comments

@lcmgh
Copy link

lcmgh commented Jul 10, 2023

Use case: Usage of the library in an environment with various OIDC providers

@06chaynes
Copy link
Owner

I'm not against adding support for multiple issuers, but it does increase the complexity a bit. A Config would either need to be shared between the issuers (might not be as helpful) or a Config would need to be provided per issuer (perhaps a bit tedious and long of tooth). Keys would also need to be stored per issuer. None of this is difficult to add but it does change the ergonomics of the library a bit.

I'll play around with this when I have a chance but would also welcome a PR to review if you are interested.

@lcmgh
Copy link
Author

lcmgh commented Jul 12, 2023

I thought about a HashMap workaround when using the "normalized" OIDC Provider URL as Key:

verifier: HashMap<String, Verifier>

But when trying to retrieve the verifier my code is not aware of the issuer url as the token was not yet decoded.

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