hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-8465) hadoop-auth should support ephemeral authentication
Date Fri, 01 Jun 2012 20:55:23 GMT

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

Hadoop QA commented on HADOOP-8465:
-----------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12530598/HADOOP-8465.patch
  against trunk revision .

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 1 new or modified test files.

    -1 patch.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/1070//console

This message is automatically generated.
                
> hadoop-auth should support ephemeral authentication
> ---------------------------------------------------
>
>                 Key: HADOOP-8465
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8465
>             Project: Hadoop Common
>          Issue Type: New Feature
>          Components: security
>    Affects Versions: 2.0.1-alpha
>            Reporter: Alejandro Abdelnur
>            Assignee: Alejandro Abdelnur
>             Fix For: 2.0.1-alpha
>
>         Attachments: HADOOP-8465.patch
>
>
> Currently, once a client is authenticated the generated authentication-token (& cookie)
are valid for a given (service configurable) lifespan.
> Once the authentication-token (& cookie) is issued, the authentication logic will
not be triggered until the authentication-token expires.
> This behavior does not work well with delegation tokens expected behavior where delegation
tokens can be canceled at any time.
> Having ephemeral authentication (which is check on every request) would address this
issue.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message