Wei-Chiu Chuang updated HADOOP-13548:
    Attachment: HADOOP-13548.001.patch

v01: Turns out that LdapGroupsMapping must remove a provider URI if it's a 
{{jceks://}}. So I expanded 
{{ProviderUtils#excludeIncompatibleCredentialProviders}}. If the class type 
passed in is a/subclass of {{FileSystem}}, the logic remains the same; 
otherwise, if the class type is a/subclass of {{AbstractJavaKeyStoreProvider}}, 
use it to trim provider URI differently.

Note: this patch changes the method signature of 
{{ProviderUtils#excludeIncompatibleCredentialProviders}} from {{Class<? extends 
FileSystem>}} to {{Class}}.

> Remove recursive dependencies of credential providers in LdapGroupsMapping
> --------------------------------------------------------------------------
>                 Key: HADOOP-13548
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13548
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: security
>    Affects Versions: 2.6.0
>            Reporter: Wei-Chiu Chuang
>            Assignee: Wei-Chiu Chuang
>         Attachments: HADOOP-13548.001.patch
> HADOOP-11934 discovered an infinite loop of dependencies in the use of 
> credential provider in LdapGroupsMapping. It added a new localjceks:// URI to 
> workaround the problem. The assumption is that the groups mapping is used 
> only in NameNode and that using a local credential file is not a problem.
> However, there are cases where Hadoop clients, such as Sqoop, may use hdfs:// 
> based credential provider and use LdapGroupsMapping at the same time. We 
> should use HADOOP-12846 to exclude hdfs:// URI credential providers.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org

Reply via email to