[
https://issues.apache.org/jira/browse/HADOOP-15995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16718255#comment-16718255
]
Wei-Chiu Chuang commented on HADOOP-15995:
------------------------------------------
Probably not in this jira, but it would be helpful to update the doc.
I ran into this exact same issue before when configuring
CompositeGroupsMapping, and then gave up (we don't really support this
configuration at Cloudera anyways). Sorry I should have filed a bug report
before.
> Add ldap.bind.password.alias in LdapGroupsMapping to distinguish aliases when
> using multiple providers through CompositeGroupsMapping
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-15995
> URL: https://issues.apache.org/jira/browse/HADOOP-15995
> Project: Hadoop Common
> Issue Type: Bug
> Components: common
> Reporter: Lukas Majercak
> Assignee: Lukas Majercak
> Priority: Major
> Attachments: HADOOP-15995.001.patch, HADOOP-15995.002.patch,
> HADOOP-15995.003.patch, HADOOP-15995.004.patch, HADOOP-15995.005.patch,
> HADOOP-15995.006.patch, HADOOP-15995.007.patch
>
>
> Currently, the property name hadoop.security.group.mapping.ldap.bind.password
> is used as an alias to get password from CredentialProviders. This has a big
> issue, which is that when we configure multiple LdapGroupsMapping providers
> through CompositeGroupsMapping, they will all have the same alias, and won't
> be able to be distinguished.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
