|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
I tried roling back PAM Authentcation plugin from 1.1 to 1.0. It did not resolve the issue.
I noticed that there is a plugin called "Matrix Authorization Strategy Plugin" currently installed at 1.1. At least on my server, This plugin can not be downgraded nor uninstalled. According to plugin page it says this plugin "Split from Jenkins core" in Oct, and a recent upgrade 1.1., released in Nov 11th, 2013, contains improvements for "Using an extension point in Jenkins 1.535." and "Better diagnosis for a form-related error" 1.535 went out Oct 14th. This look to be promising as the timing of either the "Split from Jenkins core" in Oct, or the "Matrix Authorization Strategy Plugin" would fit the timing of when we upgraded an saw this issue. Incidentally, we did try moving from "project based matrix" to "Matrix-based" and the issue was not resolved. I am unsure if "project-based matrix", and "matrix" are both manifested in "Matrix Authorization Strategy Plugin". At this point, seems they probably are.