Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3797A112B6 for ; Wed, 6 Aug 2014 03:48:13 +0000 (UTC) Received: (qmail 26546 invoked by uid 500); 6 Aug 2014 03:48:12 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 26507 invoked by uid 500); 6 Aug 2014 03:48:12 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 26339 invoked by uid 99); 6 Aug 2014 03:48:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Aug 2014 03:48:12 +0000 Date: Wed, 6 Aug 2014 03:48:12 +0000 (UTC) From: "Christopher Tubbs (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACCUMULO-3045) Support AuthenticationToken backed by CredentialProvider MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ACCUMULO-3045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14087206#comment-14087206 ] Christopher Tubbs commented on ACCUMULO-3045: --------------------------------------------- My main concern is information for users. Since you haven't fundamentally altered any internal code, I don't think this feature adds any significant change that developers should be aware of. > Support AuthenticationToken backed by CredentialProvider > -------------------------------------------------------- > > Key: ACCUMULO-3045 > URL: https://issues.apache.org/jira/browse/ACCUMULO-3045 > Project: Accumulo > Issue Type: Improvement > Components: client > Reporter: Josh Elser > Assignee: Josh Elser > Fix For: 1.6.1, 1.7.0 > > Time Spent: 50m > Remaining Estimate: 0h > > Along the same lines as ACCUMULO-2464, the MapReduce AuthenticationToken serialization also has the potential to be stored in a non-secure form. Some of this is mitigated via Base64 the password to remove human-readable-ness, the ability to serialize an AuthenticationToken to a file, etc. > Wiring up a CredentialProvider as an AuthenticationToken is another option provided to us by Hadoop likely to handle tricky security-related concerns for us. -- This message was sent by Atlassian JIRA (v6.2#6252)