Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Wed, 1 May 2013 17:42:17 +0000 (UTC)
From: "Larry McCay (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12645663.1367430127746.255657.1367430137582@arcas>
In-Reply-To: <JIRA.12645663.1367430127746@arcas>
References: <JIRA.12645663.1367430127746@arcas>
Subject: [jira] [Created] (HADOOP-9535) HSSO Server - IDP/SP Authentication
 Endpoint Deployment
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Larry McCay created HADOOP-9535:
-----------------------------------

             Summary: HSSO Server - IDP/SP Authentication Endpoint Deployment
                 Key: HADOOP-9535
                 URL: https://issues.apache.org/jira/browse/HADOOP-9535
             Project: Hadoop Common
          Issue Type: Sub-task
          Components: security
            Reporter: Larry McCay


This effort will result in an embedded Jetty based server that deploys endpoints for the authentication or federation of entities.

It will leverage common facilities for authentication and federation providers within servlet filters which allow composability of various provider types to satisfy various token and authentication processing requirements.

For instance:

In order for a client application to authenticate using BASIC credentials and receive a token that will allow access to HDFS we may need to provide a couple an endpoint comprised of an authentication provider and a token generation provider:

1. BASIC->LDAP Authentication Provider
2. Access Token Generation Provider

This allows a user to authentication to the HSSO service endpoint with simple username/password using HTTP BASIC and leverage a simple username bind to an LDAP server for authentication. It then uses the resulting normalized java.security.Subject to generate an access token for the user to pass along with subsequent requests to other Hadoop services.

Hadoop services only need to verify the token validity and trust of the issuer - HSSO service - in order to authenticate access to its protected resources.

This task is dependent on common authentication provider frameworks and will need to insure compatibility and the composability described in this task.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira