[ https://issues.apache.org/jira/browse/HADOOP-10786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14696817#comment-14696817 ]
Hudson commented on HADOOP-10786: --------------------------------- FAILURE: Integrated in Hadoop-Yarn-trunk-Java8 #287 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/287/]) HADOOP-10786. Fix UGI#reloginFromKeytab on Java 8. Contributed by Stephen Chu. (vinayakumarb: rev 24a11e39960696d75e58df912ec6aa7283be194d) * hadoop-common-project/hadoop-common/CHANGES.txt HADOOP-10786. Fix UGI#reloginFromKeytab on Java 8. Contributed by Stephen Chu. (vinayakumarb: rev e7aa81394dce61cc96d480e21204263a5f2ed153) * hadoop-common-project/hadoop-common/CHANGES.txt > Fix UGI#reloginFromKeytab on Java 8 > ----------------------------------- > > Key: HADOOP-10786 > URL: https://issues.apache.org/jira/browse/HADOOP-10786 > Project: Hadoop Common > Issue Type: Bug > Components: security > Affects Versions: 2.6.0 > Reporter: Tobi Vollebregt > Assignee: Stephen Chu > Fix For: 2.6.1, 2.7.0 > > Attachments: HADOOP-10786.2.patch, HADOOP-10786.3.patch, > HADOOP-10786.3.patch, HADOOP-10786.4.patch, HADOOP-10786.5.patch, > HADOOP-10786.patch > > > Krb5LoginModule changed subtly in java 8: in particular, if useKeyTab and > storeKey are specified, then only a KeyTab object is added to the Subject's > private credentials, whereas in java <= 7 both a KeyTab and some number of > KerberosKey objects were added. > The UGI constructor checks whether or not a keytab was used to login by > looking if there are any KerberosKey objects in the Subject's private > credentials. If there are, then isKeyTab is set to true, and otherwise it's > set to false. > Thus, in java 8 isKeyTab is always false given the current UGI > implementation, which makes UGI#reloginFromKeytab fail silently. > Attached patch will check for a KeyTab object on the Subject, instead of a > KerberosKey object. This fixes relogins from kerberos keytabs on Oracle java > 8, and works on Oracle java 7 as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)