-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Jenkins v. 2.32.2, ldap-plugin v.1.14
Two individuals can no longer be authenticated to log into Jenkins. They are members of an extremely large number (about 950) of LDAP groups. They have found other applications causing the same problem because those applications have an upper limit on the number of groups that can be scanned for authentication. Does the ldap-plugin have any such limitations? What can we check to see if this is the issue or something else is causing the problem?
Is there something I can edit in their config.xml file, /var/lib/Jenkins/users/<user id>/config.xml, that would mitigate this?
The error message received is simply "Invalid login information. Please try again". We are still scouring the logs for any useful messages.
[JENKINS-48391] LDAP Failure Members in too many Groups
| Description |
Original:
Two individuals can no longer be authenticated to log into Jenkins. They are members of an extremely large number of LDAP groups. They have found other applications causing the same problem because those applications have an upper limit on the number of groups that can be scanned for authentication. Does the ldap-plugin have any such limitations? What can we check to see if this is the issue or something else is causing the problem? The error message received is simply "Invalid login information. Please try again". We are still scouring the logs for any useful messages. |
New:
Two individuals can no longer be authenticated to log into Jenkins. They are members of an extremely large number (about 950) of LDAP groups. They have found other applications causing the same problem because those applications have an upper limit on the number of groups that can be scanned for authentication. Does the ldap-plugin have any such limitations? What can we check to see if this is the issue or something else is causing the problem? Is there something I can edit in their config.xml file, /var/lib/Jenkins/users/<user id>/config.xml, that would mitigate this? The error message received is simply "Invalid login information. Please try again". We are still scouring the logs for any useful messages. |
| Assignee | Original: Kohsuke Kawaguchi [ kohsuke ] |