Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Mon, 4 Feb 2013 22:28:13 +0000 (UTC)
From: "John Vines (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12629363.1359163085720.242043.1360016893023@arcas>
In-Reply-To: <JIRA.12629363.1359163085720@arcas>
References: <JIRA.12629363.1359163085720@arcas>
Subject: [jira] [Commented] (ACCUMULO-996) explore exposing accumulo token
 in proxy
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

John Vines commented on ACCUMULO-996:
-------------------------------------

[~ctubbsii] has pointed out that there are inconvenient session management issues that need to be handled in the proxy if we use session IDs. Instead, we can get rid of any unecessary session management issues while maintaining code simplicity by having login() spit back the serialized token instead of a session which maps to the token in the proxy.
                
> explore exposing accumulo token in proxy
> ----------------------------------------
>
>                 Key: ACCUMULO-996
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-996
>             Project: Accumulo
>          Issue Type: Sub-task
>          Components: proxy
>            Reporter: Keith Turner
>            Assignee: John Vines
>             Fix For: 1.5.0
>
>
> with the new security related changes for 1.5, do the new authentication mechanism need to be exposed in the proxy?

--
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