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

Feature request: Add support for private_key_jwt as an alternative to client_secret #207

Open

tam116 opened this issue Jul 15, 2022 · 0 comments

tam116 commented Jul 15, 2022

Microsoft is strongly pushing to use x509 based client authentication, see: https://devblogs.microsoft.com/microsoft365dev/client-secret-expiration-now-limited-to-a-maximum-of-two-years

It would be great if the ODIC/JWT auth plugin in Vault could support this part of the OIDC spec: https://openid.net/specs/openid-connect-core-1_0.html#ClientAuthentication

I would assume that Vault would generate the private key and never expose it to the operator.
The public key should be retrievable via UI and API.

Thanks,
Tyler

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment