Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
Platform: All, OS: Linux
Description
Currently Hudson only checks for attribute member in LDAP groups. However, it is
also quite common to use attribtute uniqueMember to store member list.
In WEB-INF/security/LDAPBindSecurityRealm.groovy, an one-line change that makes
Hudson search for both member=
can be done as follows:
authoritiesPopulator(DeferredCreationLdapAuthoritiesPopulator,initialDirContextFactory,"ou=groups")
{
// groupRoleAttribute = "ou";
groupSearchFilter = "(|(member=
))"
}
Thanks to Kohsuke.Kawaguchi@sun.com for the above code.
Attachments
Issue Links
- is duplicated by
-
JENKINS-2314 Supporting uniqueMember in LDAP
-
- Closed
-
Code changed in hudson
{0}User: : mindless
Path:
trunk/hudson/main/war/resources/WEB-INF/security/LDAPBindSecurityRealm.groovy
trunk/www/changelog.html
http://fisheye4.cenqua.com/changelog/hudson/?cs=16009
Log:
[FIXED JENKINS-2256] DeferredCreationLdapAuthoritiesPopulator was deprecated
in 1.280, so the groupSearchFilter used there was lost. Moved this to
groovy file so the uniqueMember query works again, and changed
to
{1}in the memberUid query to fix that one.