-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Platform: All, OS: Linux
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.
- is duplicated by
-
JENKINS-2314 Supporting uniqueMember in LDAP
-
- Closed
-
[JENKINS-2256] Hudson Does not Check uniqueMember within LDAP Groups
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Resolution | Original: Fixed [ 1 ] | |
Status | Original: Resolved [ 5 ] | New: Reopened [ 4 ] |
Status | Original: Reopened [ 4 ] | New: Open [ 1 ] |
Our organisation uses 'memberUid', so while your at it, could you add this as
well? Of course, configuration options as proposed by Issue 1909 would be fine
as well.