geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashish Jain (JIRA)" <j...@apache.org>
Subject [jira] Closed: (GERONIMO-5692) Unlock keystore command line utility does not work with Configured Encryption
Date Fri, 19 Nov 2010 11:55:13 GMT

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

Ashish Jain closed GERONIMO-5692.
---------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 2.2.2)
                       (was: 3.0)

Thank you Ashok and Forrest for your test results. I will open a new track for 2.2 and 3.0.

> Unlock keystore command line utility does not work with Configured Encryption
> -----------------------------------------------------------------------------
>
>                 Key: GERONIMO-5692
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-5692
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: crypto
>    Affects Versions: 2.1.6
>         Environment: Geronimo tomcat assembly g 2.1.6
>            Reporter: Ashish Jain
>            Assignee: Ashish Jain
>             Fix For: 2.1.7
>
>
> Steps to recreate:
> 1) Enable ConfiguredEncryption as listed by the doc https://cwiki.apache.org/GMOxDEV/obscuring-passwords.html.
> 2) Start the server
> 3)  set JAVA_OPTS=location of truststoreKeystorePassword file 
> 4)  deploy.bat unlockKeystore <name_of_the_keystore>
> it fails to unlock the keystore.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message