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 "Benoy Antony (JIRA)" <ji...@apache.org> on 2016/01/09 00:06:39 UTC
[jira] [Updated] (HADOOP-12587) Hadoop AuthToken refuses to work
without a maxinactive attribute in issued token
[ https://issues.apache.org/jira/browse/HADOOP-12587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benoy Antony updated HADOOP-12587:
----------------------------------
Attachment: HADOOP-12587-002.patch
Attaching a newer patch since the previous patch does not apply cleanly. Its a documentation change.
> 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: Benoy Antony
> Priority: Blocker
> Attachments: HADOOP-12587-001.patch, HADOOP-12587-002.patch
>
>
> 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)