Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Fri, 1 Jun 2012 20:44:23 +0000 (UTC)
From: "Alejandro Abdelnur (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <2028077315.28176.1338583463269.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <1513140608.28156.1338583223317.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Commented] (HADOOP-8465) hadoop-auth should support
 ephemeral authentication
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Alejandro Abdelnur commented on HADOOP-8465:
--------------------------------------------

This can be addressed by allowing an AuthenticationHandler to set the expiration of the authentication token to ZERO (note that only ZERO would be supported, the AuthenticationHandler cannot change to an arbitrary expiration interval).

When the expiration is set to ZERO, the AuthenticationFilter would let the request continue to the target resource but it will not issue an HTTP Cookie. This means that subsequent requests will be forced through the AuthenticationHandler.

This will work with webhdfs delegation tokens where the delegationtoken must be part of the querystring of the request.
                
> 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
>
>
> 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