|
@@ -320,6 +320,11 @@ for ldap providers in the same way as above does.
|
|
|
an LDAP server with a non-AD schema, this should be replaced with
|
|
|
(&(objectClass=inetOrgPerson)(uid={0}). {0} is a special string used to
|
|
|
denote where the username fits into the filter.
|
|
|
+
|
|
|
+ If the LDAP server supports posixGroups, Hadoop can enable the feature by
|
|
|
+ setting the value of this property to "posixAccount" and the value of
|
|
|
+ the hadoop.security.group.mapping.ldap.search.filter.group property to
|
|
|
+ "posixGroup".
|
|
|
</description>
|
|
|
</property>
|
|
|
|
|
@@ -329,7 +334,9 @@ for ldap providers in the same way as above does.
|
|
|
<description>
|
|
|
An additional filter to use when searching for LDAP groups. This should be
|
|
|
changed when resolving groups against a non-Active Directory installation.
|
|
|
- posixGroups are currently not a supported group class.
|
|
|
+
|
|
|
+ See the description of hadoop.security.group.mapping.ldap.search.filter.user
|
|
|
+ to enable posixGroups support.
|
|
|
</description>
|
|
|
</property>
|
|
|
|