-
Notifications
You must be signed in to change notification settings - Fork 23
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
Upgrading to Jenkins 2.160 breaks CAS logins #9
Comments
I am having the same issue. differences:
|
Same problem after after upgrading from 2.150.1 to 2.150.2 last night.
I don't see anything happening in the Jenkins log file while this is going on. |
Thanks for the notice. This issue is related to the SECURITY-901 fix in Jenkins. I'll try to implement the necessary adjustments in CAS plugin ASAP, until then you can either downgrade Jenkins or apply the workaround described in the Upgrade Guide. |
Ah, the upgrade guide did not mention this when I looked yesterday. Unfortunately the workaround of setting that Java property does not seem to fix it for me. But we can stay at .1 for now. |
Turns out, there was a typo in the property name on the release notes. Someone updated the wiki page and release notes and things are working for me on .2 now. Just need to remember to unset the property after the CAS plugin is updated :) |
The fix for this issue is available in jenkinsci#2, but before I release it could you please try the test build available on the CI server? (get cas-plugin.hpi, rename it to cas-plugin.jpi, put it in your Jenkins plugins folder and restart). |
@fcrespel I've tested. It's run OK. Thank you so much for you fixing. |
Not even required to rename, the |
Thanks for the feedback, CAS plugin version 1.4.3 is now released. It may take a few hours to appear in the Update Center, until then you can grab it from the Maven repository. |
Add option to customize validation URL params
Upgrading to Jenkins 2.160 (from 2.159) causes CAS logins to fail with an infinite loop, as Jenkins does not respect the result of the authorization flow. To reproduce:
Note:
The text was updated successfully, but these errors were encountered: