[
https://issues.apache.org/jira/browse/HBASE-23970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17514759#comment-17514759
]
Nick Dimiduk commented on HBASE-23970:
--------------------------------------
I spent some time debugging this, specifically in the context of
{{TestCustomSaslAuthenticationProviderSimpleRpcServer}}. It appears to me that
the HDFS cluster that is initialized for the test is run without specifying a
{{User}}/{{Principal}}. In my case, that means the test file system is
initialized by using the default {{User}} with the default
{{HadoopLoginModule}}, which resolves to the active ticket. For this user, no
name mapping rule is found, and the exception is thrown.
When expire said ticket, this file system is created instead with the local OS
user {{Principal}}. In this case, no mapping is attempted, and file system
initialization proceeds.
The applicable fall-back logic is implemented in
{{o.a.h.security.UserGroupInformation$HadoopLoginModule#commit()}}.
> TestUsersOperationsWithSecureHadoop fails when an existing ticket is present
> ----------------------------------------------------------------------------
>
> Key: HBASE-23970
> URL: https://issues.apache.org/jira/browse/HBASE-23970
> Project: HBase
> Issue Type: Test
> Components: security, test
> Affects Versions: 3.0.0-alpha-1, 2.3.0
> Reporter: Nick Dimiduk
> Priority: Minor
>
> {{TestUsersOperationsWithSecureHadoop}} makes assumptions about the state of
> the machine environment. When i have an existing ticket issued and active
> (shown via {{klist}}), this test fails. Signing out of all active sessions
> allows the test to again pass.
> {noformat}
> Caused by:
> org.apache.hadoop.security.authentication.util.KerberosName$NoMatchingRule:
> No rules applied to [email protected]
> at
> org.apache.hadoop.hbase.security.TestUsersOperationsWithSecureHadoop.testAuthUtilLogin(TestUsersOperationsWithSecureHadoop.java:146)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
