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 E3D64179EC for ; Tue, 20 Jan 2015 19:47:34 +0000 (UTC) Received: (qmail 74337 invoked by uid 500); 20 Jan 2015 19:47:34 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 74287 invoked by uid 500); 20 Jan 2015 19:47:34 -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 74271 invoked by uid 99); 20 Jan 2015 19:47:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Jan 2015 19:47:34 +0000 Date: Tue, 20 Jan 2015 19:47:34 +0000 (UTC) From: "Josh Elser (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACCUMULO-3452) Add SASL support to thrift proxy 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-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14284295#comment-14284295 ] Josh Elser commented on ACCUMULO-3452: -------------------------------------- So I didn't think this through entirely: given the current configuration, there's no way for the thrift proxy to get KRB credentials from a client and perform some action against Accumulo using them as this, by itself, would allow any user with credentials to act as another user. Hadoop does have [some precedent|http://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-common/SecureMode.html#Proxy_user] here that we might be able to adopt and leverage that restricts the users which are allowed to impersonate another. > Add SASL support to thrift proxy > -------------------------------- > > Key: ACCUMULO-3452 > URL: https://issues.apache.org/jira/browse/ACCUMULO-3452 > Project: Accumulo > Issue Type: Sub-task > Components: proxy > Reporter: Josh Elser > Assignee: Josh Elser > Fix For: 1.7.0 > > > The thrift proxy doesn't leverage TServerUtils (and instead creates a THsHaServer by hand). This means it won't automatically create the correct thrift server (also the reason it doesn't support SSL). -- This message was sent by Atlassian JIRA (v6.3.4#6332)