[ http://issues.apache.org/jira/browse/GERONIMO-2049?page=all ]
Paul McMahan updated GERONIMO-2049:
-----------------------------------
Attachment: GERONIMO-2049.patch
Aaron, I was working on a patch for this issue when I saw your commit go
through. I realize that you already consider the issue to be resolved but I
thought you still might want to take a peek at the patch because it addresses
one additional problem not covered by your commit AFAICT. The problem is that
if there are multiple keystores/truststores available when the editHTTPS.jsp
form is loaded then the stores that are currently in use by the connector are
not necessarily selected by default (even though they are available in the drop
down list). An unwary user could accidentally change the keystore/truststore
if they are not paying close attention. The patch also removes some unneeded
code.
> Jetty HTTPS edit shows no keystores in list
> -------------------------------------------
>
> Key: GERONIMO-2049
> URL: http://issues.apache.org/jira/browse/GERONIMO-2049
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: web, security, console
> Versions: 1.1
> Reporter: Aaron Mulder
> Assignee: Aaron Mulder
> Priority: Blocker
> Fix For: 1.1
> Attachments: GERONIMO-2049.patch
>
> When adding a new HTTPS connector in Jetty, it shows a drop-down of available
> unlocked keystores with at least one private key.
> When editing the same keystore, the keystore list is empty.
--
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
