-
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
com.nimbusds.jose.proc.BadJOSEException: Signed JWT rejected: Another algorithm expected, or no matching key(s) found #438
Comments
The exception from pac4j is missing details (there's a loop where it tries all supported methods then throws an exception but throws away all the others from the loop which contains the interesting one) Enabling finer logging on |
I can't find an option or documentation on increase log level, did I miss something? or did you mean a custom build with added logs? |
From what I understand of those fine logs, there's a 'time ahead of current time' issue, So I guess a timezone or NTP issue on our server.
I wish we had more details on the actual values observed. |
there is a clock skew option you can use, but the timezone should not matter as the times are always in seconds since a well known epoc which is zoneless. Alas the library offers no more information here :( But as this token was generated in the future either your Jenkins instance is running in the past or your OIDC server is running in the future. you should be able to see the clock time of your OIDC server by inspecting the HTTP headers when you login to it (or visit any dynamic page on the site). and you should be able to get the data of your Jenkins server as you are an admin of it :) this can give you an indication if something is out of sync, and give you a value of difference that you may want to use for the clockskew parameter if 60 seconds is not enough |
My laptop was about 80 s ahead of the Jenkins server, so I've forced an clock sync on the server. I'm used to Kerberos clock screw tolerance of 300 s, so I wasn't expecting a clock issue here initially. |
Thanks for the update. |
Jenkins and plugins versions report
Environment
What Operating System are you using (both controller, and any agents involved in the problem)?
Windows Server 2022
Reproduction steps
Expected Results
Works like before, or at least provide meaningful logs
Actual Results
Jenkins shows a generic "A problem occurred while processing the request"
Logs refer to an algorythm or kid mismatch in JWT from what I could understand:
Anything else?
I couldn't find documentation or settings to move forward on this issue:
Are you interested in contributing a fix?
No response
The text was updated successfully, but these errors were encountered: