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 B44B7E258 for ; Tue, 18 Dec 2012 16:26:14 +0000 (UTC) Received: (qmail 55129 invoked by uid 500); 18 Dec 2012 16:26:14 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 55060 invoked by uid 500); 18 Dec 2012 16:26:13 -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 54992 invoked by uid 99); 18 Dec 2012 16:26:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Dec 2012 16:26:13 +0000 Date: Tue, 18 Dec 2012 16:26:13 +0000 (UTC) From: "John Vines (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (ACCUMULO-912) getConnector in MockAccumulo clobber's existing user authorizations 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-912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Vines updated ACCUMULO-912: -------------------------------- Affects Version/s: (was: 1.4.3) > getConnector in MockAccumulo clobber's existing user authorizations > ------------------------------------------------------------------- > > Key: ACCUMULO-912 > URL: https://issues.apache.org/jira/browse/ACCUMULO-912 > Project: Accumulo > Issue Type: Bug > Components: client > Affects Versions: 1.4.1, 1.4.2 > Reporter: John Vines > Assignee: John Vines > Fix For: 1.5.0, 1.4.3 > > > If a user exists in MockAccumulo with a set of authorizations, and you do a getConnector for the user, it will clobber that user's authorizations and remake them. It should do a check before creating the internal user object. On top of that, it should also check the password if the user does exist. -- 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