[
https://issues.apache.org/jira/browse/HADOOP-8465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294074#comment-13294074
]
Hudson commented on HADOOP-8465:
--------------------------------
Integrated in Hadoop-Hdfs-trunk-Commit #2425 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/2425/])
HADOOP-8465. hadoop-auth should support ephemeral authentication (tucu)
(Revision 1349613)
Result = SUCCESS
tucu : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1349613
Files :
*
/hadoop/common/trunk/hadoop-common-project/hadoop-auth/src/main/java/org/apache/hadoop/security/authentication/server/AuthenticationFilter.java
*
/hadoop/common/trunk/hadoop-common-project/hadoop-auth/src/main/java/org/apache/hadoop/security/authentication/server/AuthenticationToken.java
*
/hadoop/common/trunk/hadoop-common-project/hadoop-auth/src/test/java/org/apache/hadoop/security/authentication/server/TestAuthenticationFilter.java
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
> 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, 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
