hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-12587) Hadoop auth token refused to work without a maxinactive attribute in a kerberos token
Date Thu, 19 Nov 2015 14:57:11 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-12587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15013647#comment-15013647
] 

Steve Loughran commented on HADOOP-12587:
-----------------------------------------

The Hadoop 2.6 timeline service isn't setting the max-inactive attribute which HADOOP-12050
now requires. As a result, a 2.7.1+ client cannot submit work to a Hadoop 2.6 cluster (and
presumably, a 2.7.0 cluster). 

> Hadoop auth token refused to work without a maxinactive attribute in a kerberos token
> -------------------------------------------------------------------------------------
>
>                 Key: HADOOP-12587
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12587
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: security
>    Affects Versions: 2.7.1
>         Environment: OSX heimdal kerberos client against Linux KDC -talking to a Hadoop
2.6.0 cluster
>            Reporter: Steve Loughran
>            Priority: Blocker
>
> If you don't have a max-inactive attribute in your kerberos token, 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)

Mime
View raw message