You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Ashish Jain (JIRA)" <ji...@apache.org> on 2010/04/27 10:28:36 UTC
[jira] Commented: (GERONIMO-5180) Deployer unlockKeystore command
cannot be utilized if keystore is created through Java provided KeyTool
[ https://issues.apache.org/jira/browse/GERONIMO-5180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12861310#action_12861310 ]
Ashish Jain commented on GERONIMO-5180:
---------------------------------------
Applied to 2.2 branch @ revision: 938356
> Deployer unlockKeystore command cannot be utilized if keystore is created through Java provided KeyTool
> -------------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-5180
> URL: https://issues.apache.org/jira/browse/GERONIMO-5180
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Affects Versions: 2.1.5, 2.2.1, 3.0
> Environment: geronimo tomcat assembly
> Reporter: Ashish Jain
> Assignee: Ashish Jain
> Fix For: 2.1.5, 2.2.1, 3.0
>
>
> Here are the steps to recreate this issue:
> 1) Create a keystore using keytool.exe available in JAVA_HOME/bin.
> 2) Now use the command "deploy unlockKeystore <Keystore_Name>"
> An exception is thrown suggesting "keystore does not exist".
> To overcome this exception access the admin console keystore portlet, this operation will add the newly created keystore as a gbean into geronimo.
> Now try #2 unlock will be successful.
> To fix this issue up there are 2 possibilities on which I will put up a discussion on dev list.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.