Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Fri, 16 May 2014 16:53:16 +0000 (UTC)
From: "Christopher Tubbs (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12714669.1400199003074.369423.1400259196236@arcas>
In-Reply-To: <JIRA.12714669.1400199003074@arcas>
References: <JIRA.12714669.1400199003074@arcas>
Subject: [jira] [Updated] (ACCUMULO-2818) generate_monitor_certificate
 creates bad keystore
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Christopher Tubbs updated ACCUMULO-2818:
----------------------------------------

    Affects Version/s: 1.5.1

> generate_monitor_certificate creates bad keystore
> -------------------------------------------------
>
>                 Key: ACCUMULO-2818
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2818
>             Project: Accumulo
>          Issue Type: Bug
>          Components: monitor
>    Affects Versions: 1.5.1, 1.6.0
>            Reporter: Christopher Tubbs
>            Assignee: Christopher Tubbs
>             Fix For: 1.5.2, 1.6.1, 1.7.0
>
>         Attachments: ACCUMULO-2818.v1.patch
>
>
> The keytool command in the generate_monitor_certificate.sh script creates a keystore with a different passphrase than the key it contains. This is a bit non-standard and has problems in some environments (Jetty).
> The keystore and the truststore should have different passwords, but the key inside the keystore should have the same password as the keystore itself. This is what Jetty expects.


--
This message was sent by Atlassian JIRA
(v6.2#6252)