From issues-return-31714-archive-asf-public=cust-asf.ponee.io@geode.apache.org Fri Feb 23 17:14:05 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id AB0C318077A for ; Fri, 23 Feb 2018 17:14:04 +0100 (CET) Received: (qmail 15637 invoked by uid 500); 23 Feb 2018 16:14:03 -0000 Mailing-List: contact issues-help@geode.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@geode.apache.org Delivered-To: mailing list issues@geode.apache.org Received: (qmail 15625 invoked by uid 99); 23 Feb 2018 16:14:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Feb 2018 16:14:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 382BB180375 for ; Fri, 23 Feb 2018 16:14:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.511 X-Spam-Level: X-Spam-Status: No, score=-109.511 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id 2thXEG5S17of for ; Fri, 23 Feb 2018 16:14:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 796365F571 for ; Fri, 23 Feb 2018 16:14:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 9BFD8E0117 for ; Fri, 23 Feb 2018 16:14:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 4B1432140E for ; Fri, 23 Feb 2018 16:14:00 +0000 (UTC) Date: Fri, 23 Feb 2018 16:14:00 +0000 (UTC) From: "Barbara Pruijn (JIRA)" To: issues@geode.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (GEODE-4691) Gfsh command Start Locator shows inconsistent behavior with auto-connecting with a Security Manager MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/GEODE-4691?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:all-tabpanel ] Barbara Pruijn updated GEODE-4691: ---------------------------------- Fix Version/s: 1.5.0 > Gfsh command Start Locator shows inconsistent behavior with auto-connecti= ng with a Security Manager > -------------------------------------------------------------------------= -------------------------- > > Key: GEODE-4691 > URL: https://issues.apache.org/jira/browse/GEODE-4691 > Project: Geode > Issue Type: Bug > Components: docs, gfsh, security > Reporter: Barbara Pruijn > Priority: Major > Labels: pull-request-available > Fix For: 1.5.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > When starting a locator in gfsh like this > {code:java} > start locator --name=3Dlocator1{code} > the default behavior is to auto-connect gfsh to the locator. > From the gfsh start locator help: > {code:java} > connect > When connect is set to false , Gfsh does not automatically connect to the= locator which is started > using this command. > Required: false > Default (if the parameter is specified without value): true > Default (if the parameter is not specified): true{code} > When starting the locator with a Security Manager like this > {code:java} > start locator --name=3Dlocator1 --J=3D-Dgemfire.security-manager=3Dorg.ap= ache.geode.examples.SimpleSecurityManager{code} > The result is that gfsh does not auto connect to the locator. However thi= s is not listed in the help command and is inconsistent in the user expecta= tion. > =C2=A0 > Solution and accceptance criteria: > Update the output of=C2=A0 > {code:java} > start locator --J=3D-Dgemfire.security-manager=3Dorg.apache.geode.example= s.SimpleSecurityManager{code} > to indicate that it is not auto-connected. New output: > {code:java} > Security Manager is enabled - unable to auto-connect. Please use connect = with --user and --password to connect to locator.{code} > Update gfsh help to correctly list the behavior when the Security Manager= is set via the --J parameter > =C2=A0 > gfsh should display correct connect help message for > {code:java} > help start locator{code} > when using Security Manager. > {code:java} > connect > When connect is set to false or when locator is started with a security m= anager using --J=3D-Dgemfire.security-manager option, Gfsh does not automat= ically connect to the locator which is started using this command. > Required: false > Default (if the parameter is specified without value): true > Default (if the parameter is not specified): true{code} > =C2=A0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)