-
Notifications
You must be signed in to change notification settings - Fork 95
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
Failed to refresh expired token #477
Comments
We use keycloak for some systems and it is working for refresh here which suggests (along with the exception) that this is environmental. |
It might be the environment. How can I be sure? Sometimes it's enough to click on "Dashboard" again and to be logged in. Sometime, one needs to clear all cookies before login works again. Thanks for your help. |
The default is 5 seconds and it is not currently user configurable. This should be good enough, and any longer would indicate downstream issues.
Cookies should not affect this, so I would sumize either there is a distinct issue with cookies (but that would generally result in HTTP Headers too Large from Jenkins) or it is coincidental.
The why is on keycloaks side (or the token server keycloak has told us to use.)
If keycloak is too slow which this indicates focus on that not Jenkins. There can be many reasons keycloak is slow depending on your deployment model and resources allocated to it, or even underlying authentication providers |
Jenkins and plugins versions report
Environment
What Operating System are you using (both controller, and any agents involved in the problem)?
It's a docker deployment based on "jenkins/jenkins:lts-jdk21"
Reproduction steps
I've configured OIDC via CasC. The OIDC server is a Keycloak cluster:
Expected Results
The page loads and I can continue to work.
Actual Results
I get an error page.
In the logs I can find an error and exception:
Anything else?
This was working before. Unfortunatelly, I can't pin the exact time when it stopped working.
Are you interested in contributing a fix?
No response
The text was updated successfully, but these errors were encountered: