You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2016/01/26 19:22:39 UTC

[jira] [Created] (HADOOP-12742) pull out logic to determine principal, allow kdiag to get at it directly

Steve Loughran created HADOOP-12742:
---------------------------------------

             Summary: pull out logic to determine principal, allow kdiag to get at it directly
                 Key: HADOOP-12742
                 URL: https://issues.apache.org/jira/browse/HADOOP-12742
             Project: Hadoop Common
          Issue Type: Sub-task
          Components: security
    Affects Versions: 2.8.0
            Reporter: Steve Loughran


The process for determining the principal name on a login is convoluted, and can behave differently across JVMs. If it's playing up, it's hard to work out what is up.

I propose
# pull out the code to something accessible by kdiag
# have it return the principal, and a string describing the origin of the principal (env var, canonical principal, JVM introspection). This can be logged and validated in KDiag, logged @ debug and used in UGI



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)