[jira] Updated: (GERONIMO-481) HTTPS Connector should work with a keystore GBean

["Aaron Mulder (JIRA)" <de...@geronimo.apache.org>]

     [ http://issues.apache.org/jira/browse/GERONIMO-481?page=all ]

Aaron Mulder updated GERONIMO-481:
----------------------------------

    Fix Version: 1.0
    Description: 
It currently looks directly at the keystore file.

We should have a GBean manage the certificates just using the file for persistence if necessary. The HTTPS connector should then get its certs from the GBean.

  was:
It currently looks directly at the keystore file.

We should have a GBean manage the certificates just using the file for persistence if necessary. The HTTPS connector should then get its certs from the GBean.

    Environment: 

Subsequent comments on the mailing list suggested that we have a socket factory instead of a GBean that will produce a private key or keystore password on request.  Perhaps this issue should be closed or changed accordingly?

In any case, the issue is present for at least Jetty and Tomcat, and it would be nice if OpenEJB and ActiveMQ and other products had an easy way to support SSL connections via the same mechanism.

> HTTPS Connector should work with a keystore GBean
> -------------------------------------------------
>
>          Key: GERONIMO-481
>          URL: http://issues.apache.org/jira/browse/GERONIMO-481
>      Project: Geronimo
>         Type: Improvement
>     Reporter: Jeremy Boynes
>      Fix For: 1.0

>
> It currently looks directly at the keystore file.
> We should have a GBean manage the certificates just using the file for persistence if necessary. The HTTPS connector should then get its certs from the GBean.

-- 
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