Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Date: Mon, 7 Nov 2011 09:23:52 +0000 (UTC)
From: =?utf-8?Q?Michael_He=C3=9F_=28Created=29_=28JIRA=29?= <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: 
 <1249560640.6124.1320657832275.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (CXF-3895) add support for Jetty's password
 obfuscation methods
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

add support for Jetty's password obfuscation methods
----------------------------------------------------

                 Key: CXF-3895
                 URL: https://issues.apache.org/jira/browse/CXF-3895
             Project: CXF
          Issue Type: Improvement
          Components: Configuration
    Affects Versions: 2.4.2
         Environment: Java 6
Windows XP SP3
CXF 2.4.2
            Reporter: Michael He=C3=9F
            Priority: Minor


For SSL connectors, the Jetty configuration allows definition of keystore a=
nd truststore passwords in a obfuscated fashion. See http://wiki.eclipse.or=
g/Jetty/Howto/Secure_Passwords for details. Currently this does not work wh=
en using the Spring based configuration for jetty, i.e. using for example t=
his

<sec:keyStore type=3D"JKS" password=3D"OBF:1sot1v961saj1v9i1v941sar1v9g1sox=
" file=3D"conf/keystore" />

will lead to an exception on startup, which is identical to those that come=
 up when an invalid keystore password is provided.

My guess is, that the "OBF:" prefix is not detected by the configuration ho=
ok, and therefore the provided password string is used as-is. (But I am jus=
t guessing here...)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp=
a
For more information on JIRA, see: http://www.atlassian.com/software/jira