[ http://issues.apache.org/jira/browse/GERONIMO-1097?page=comments#action_12358264 ]
Aaron Mulder commented on GERONIMO-1097: ---------------------------------------- I'm not so sure about this. In the long term, I'd like the keystore portlet to be able to edit any keystore, using a more generic keystore service and requiring the console user to enter the keystore password when appropriate. In the short term, it's not bad to use the portlet to prepare keystore-1 and then manually copy it over keystore -- I'm not sure how good an idea it is to muck with the sample keystore in place. Especially because the password is (I believe) hardcoded into the console deployment plan, so if you plan to edit the main keystore with the console, you can never change the password on it. > (Patch) Keystore Portlet should point to the default keystore file instead of > ssl-keystore-1 > -------------------------------------------------------------------------------------------- > > Key: GERONIMO-1097 > URL: http://issues.apache.org/jira/browse/GERONIMO-1097 > Project: Geronimo > Type: Bug > Components: console > Versions: 1.0 > Environment: Win32 w/ 1.4.2 JDK > Reporter: Donald Woods > Assignee: Donald Woods > Attachments: Geronimo-1097.patch > > The current Keystore portlet which was just integrated using G-887, does not > use the default var\security\keystore file, but instead creates a new file > var\security\ssl-keystore-1 > Since we want users to be able to replace the default self-signed SSL > certificate with either one they create or purchase, we should point the > Keystore portlet to the existing keystore file. Otherwise, the portlet is > useless, since it will require a plan change and redeploy before the new > ssl-keystore-1 file can be used. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
