@Paulina, Long journey, so I hope this does the trick. While not exposed in Cloudera Manager, you can identify an alternative userid attribute. By default, for posix objecdts, the default is memberUid (which won't work for you unless memberUid contains the numeric id). Try this: - In Cloudera Manager, navigate to: Clusters --> HDFS --> Configuration - Search for: Cluster-wide Advanced Configuration Snippet (Safety Valve) for core-site.xml - Add the following: Name: hadoop.security.group.mapping.ldap.posix.attr.uid.name Value: uid - Save - Restart the cluster (so the servers can detect the new settings) BACKGROUND: As you observed, by default HDFS assumes that the memberUid attribute will have a value of the uidNumber of the user account. The configuration I mentioned above lets you adjust this so that rather than searching for "memberUid=1004" the search will contain "uid=maslova" You can find more information here: https://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-common/core-default.xml#hadoop.security.group.mapping.ldap.posix.attr.uid.name This is the description: "The attribute of posixAccount to use when groups for membership. Mostly useful for schemas wherein groups have memberUids that use an attribute other than uidNumber." As you can see, the configuration for hdfs meets the needs of your situation. Cheers, Ben
... View more
