You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: