[
https://issues.apache.org/jira/browse/HADOOP-12587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15033443#comment-15033443
]
Steve Loughran commented on HADOOP-12587:
-----------------------------------------
I wasn't actually going to work on it at all, once I'd found the problem I was
opening the bug and hoping it'd get fixed before I'd had revert the original
bug prior to 2.8 shipping. So yes, I would be grateful. The current patch
exists purely to diagnose the problem and track it down if it re-occurs.
fix wise, something that splits up into "required" and "optional" attrs is
enough, with a test
> Hadoop AuthToken refuses to work without a maxinactive attribute in issued
> token
> --------------------------------------------------------------------------------
>
> Key: HADOOP-12587
> URL: https://issues.apache.org/jira/browse/HADOOP-12587
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 2.8.0
> Environment: OSX heimdal kerberos client against Linux KDC -talking
> to a Hadoop 2.6.0 cluster
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Blocker
>
> If you don't have a max-inactive attribute in the auth token returned from
> the web site, AuthToken will raise an exception. This stops callers without
> this token being able to submit jobs to a secure Hadoop 2.6 YARN cluster with
> timeline server enabled.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
