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

JWT auth fails after EKS OIDC provider's key rotation #11611

Closed
yuchun0228 opened this issue May 14, 2021 · 2 comments
Closed

JWT auth fails after EKS OIDC provider's key rotation #11611

yuchun0228 opened this issue May 14, 2021 · 2 comments
Assignees
Labels
bug Used to indicate a potential bug ecosystem
Milestone

Comments

@yuchun0228
Copy link

yuchun0228 commented May 14, 2021

We use EKS Service Account Token to login in Vault. The login fails after key rotation at EKS OIDC provider with message:
“* error validating token: error verifying token signature: failed to verify id token signature”

I tried to debug and found Vault is using an older version (v2.2.1) of go-oidc library which contains a bug regarding key rotation strategy that has been solved in v3.0.0.
Without the fix, since EKS OIDC provider returns "cache-control: max-age=604800" in the http header, go-oidc sets 7 days expiration for each remoteKeySet and does NOT fetch keys even if cannot find a key in the remoteKeySet.

Please upgrade the depended go-oidc version.

@kalafut
Copy link
Contributor

kalafut commented May 18, 2021

Thanks for this report! We're aware of the issue and are preparing a dependency update.

cc: @austingebauer

@austingebauer
Copy link
Contributor

Hi, @yuchun0228. We've updated the underlying go-oidc library version to address this issue. It will land in the 1.7.3 release of Vault. Thank you again for the report. Closing this issue now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Used to indicate a potential bug ecosystem
Projects
None yet
Development

No branches or pull requests

4 participants