Mailing-List: contact issues-help@geode.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geode.incubator.apache.org
Date: Mon, 10 Oct 2016 22:36:20 +0000 (UTC)
From: "Kevin Duling (JIRA)" <jira@apache.org>
To: issues@geode.incubator.apache.org
Message-ID: <JIRA.13009311.1475521000000.787899.1476138980556@Atlassian.JIRA>
In-Reply-To: <JIRA.13009311.1475521000000@Atlassian.JIRA>
References: <JIRA.13009311.1475521000000@Atlassian.JIRA> <JIRA.13009311.1475521000114@arcas>
Subject: [jira] [Updated] (GEODE-1959) Prompt for username and password when
 adding a member
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 10 Oct 2016 22:36:25 -0000


     [ https://issues.apache.org/jira/browse/GEODE-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kevin Duling updated GEODE-1959:
--------------------------------
    Attachment: security.json
                gemfire.properties

Configuration files needed to reproduce problem

> Prompt for username and password when adding a member
> -----------------------------------------------------
>
>                 Key: GEODE-1959
>                 URL: https://issues.apache.org/jira/browse/GEODE-1959
>             Project: Geode
>          Issue Type: Improvement
>          Components: security
>            Reporter: Diane Hardman
>            Assignee: Kevin Duling
>         Attachments: gemfire.properties, security.json
>
>
> When you have SecurityManager configured as part of starting a locator, the administrator currently needs to have either AuthInitialize implemented or have stored credentials (in plain text) in geode.properties file. In the case where neither AuthInitialize is implemented NOR are there any credentials stored in geode.properties, then the administrator should be prompted for username and password when attempting to start another member in the distributed system.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)