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
After upgrading from 1.0.0 to 2.1.0 I found the provider looping continuously on a OIDC AuthBackend: 2025/01/24 13:28:14 [INFO] JWT/OIDC Auth '"azure"' tune configuration changed
From the metrics I can see on version 1.0.0 there were no reconciliations.
Not sure if that helps, but we actually don't set any tune since it's not required according to the CRD, yet drift detection thinks this configuration should be constantly synced..
2025/01/29 12:04:56 [INFO] JWT/OIDC Auth '"oidc"' tune configuration changed
2025/01/29 12:04:56 [DEBUG] Writing oidc auth tune to '"oidc"'
2025/01/29 12:04:56 [INFO] Written oidc auth tune to "oidc"
2025/01/29 12:04:56 [DEBUG] Reading auth oidc from Vault
2025/01/29 12:04:56 [DEBUG] Reading jwt auth tune from "oidc/tune"
2025/01/29 12:04:56 [DEBUG] Reading auth oidc from Vault
2025/01/29 12:04:56 [DEBUG] Reading jwt auth tune from "oidc/tune"
2025/01/29 12:04:56 [DEBUG] Updating auth oidc in Vault
This repeats about 10 times per second rendering the auth backend unusable.
What happened?
After upgrading from 1.0.0 to 2.1.0 I found the provider looping continuously on a OIDC AuthBackend:
2025/01/24 13:28:14 [INFO] JWT/OIDC Auth '"azure"' tune configuration changed
From the metrics I can see on version 1.0.0 there were no reconciliations.
My resource is the following:
To fix it I had to copy the
tune
config from the status, changing it from:to:
How can we reproduce it?
Just create a JWT/OIDC AuthBackend and set a
tune
configuration with a single value.What environment did it happen in?
Vault 1.15.5.
Provider 2.1.0
The text was updated successfully, but these errors were encountered: