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

Posted to notifications@accumulo.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2017/06/28 23:41:00 UTC

[jira] [Created] (ACCUMULO-4671) ConfiguratorBase.unwrapAuthenticationToken will NPE if the Token is not in the Job's credentials

Josh Elser created ACCUMULO-4671:
------------------------------------

             Summary: ConfiguratorBase.unwrapAuthenticationToken will NPE if the Token is not in the Job's credentials
                 Key: ACCUMULO-4671
                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4671
             Project: Accumulo
          Issue Type: Bug
          Components: mapreduce
            Reporter: Josh Elser
            Assignee: Josh Elser
             Fix For: 1.7.4, 1.8.2, 2.0.0


When Kerberos is enabled, the AuthenticationToken set on the Configuration object is essentially a pointer to the Hadoop-style Token stored (securely) in the Job's credentials object.

However, if by user error, the user thinks that they have serialized a Token (but it got lost along the way), unwrapAuthenticationToken will throw an NPE trying to extract that token. The name of the Token is abstracted away from the user (they shouldn't actually know what it is), so we should not fail hard like this.

It would be easy to return back the original token in this case and update the javadoc accordingly to warn users.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)