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

Hashicorp Vault OIDC identity provider #13

Closed
mofr93 opened this issue Oct 21, 2024 · 3 comments
Closed

Hashicorp Vault OIDC identity provider #13

mofr93 opened this issue Oct 21, 2024 · 3 comments
Labels
enhancement New feature or request wontfix This will not be worked on

Comments

@mofr93
Copy link

mofr93 commented Oct 21, 2024

Hi,

Hashicorp vault OIDC provider issues an opaque access_token. They recommend we use the userinfo_endpoint for introspection, because the access_token itself cannot be parsed, therefore it is not working. Is there any plans to support verification of claims etc. from the userinfo_endpoint?

@sevensolutions
Copy link
Owner

Hi @mofr93
you mean the token is not a JWT token?

At the beginning of this plugin i was always using the introspection endpoint but removed it because it will be called for every single endpoint, which can slow everything down...

I have already used Vault but not as an OIDC Provider. I will have a closer look on the weekend.

@mofr93
Copy link
Author

mofr93 commented Oct 22, 2024

Hey @sevensolutions

Thanks for the reply.

Yes, the access_token is just an opaque token that is only used for calling the introspection endpoint in Vault, so no JWT. I see the problems with calling this endpoint everytime. Maybe it needs to have some sort of cache set up. I tried this other project that just verifies the id_token which works for me https://github.com/lukaszraczylo/traefikoidc

@sevensolutions sevensolutions added the enhancement New feature or request label Nov 12, 2024
@sevensolutions sevensolutions added the wontfix This will not be worked on label Dec 31, 2024
@sevensolutions
Copy link
Owner

I will close this as won't-fix, at least for now because i don't want to implement this in the near future.
I think not many are using Vault for this scenario.
If you think I'am wrong, please create a new issue with some details.

@sevensolutions sevensolutions closed this as not planned Won't fix, can't repro, duplicate, stale Dec 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants