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

Vamsavardhana Reddy updated GERONIMO-2278:
------------------------------------------

    Attachment: GERONIMO-2278.patch

GERONIMO-2278.patch:
1.  Fixes edit page so that current values show in the select boxes
2.  Changes made to keyStore and trustStore are now saved and alias is set to 
the current unlocked key in the keystore
3.  Empty string is a valid trustStore parameter, meaning the value should be 
cleared.

Q 1: Should the trustStore parameter be made optional since it is required only 
when "Client Auth" is checked?

Q 2: Even when Client Auth is checked, the trustStore parameter can be left 
empty so that something like the following takes effect

The validity is checked using the CA certificates stored in the first of these 
to be found:

   1. A keystore file specified by the javax.net.ssl.trustStore system property
   2. java-home/lib/security/jssecacerts
   3. java-home/lib/security/cacerts


> Problems in editing Jetty SSL Connector and the edit page in Geronimo Console
> -----------------------------------------------------------------------------
>
>                 Key: GERONIMO-2278
>                 URL: http://issues.apache.org/jira/browse/GERONIMO-2278
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: console
>    Affects Versions: 1.1, 1.1.1
>         Environment: Win XP, G1.1.1-SNAPHOT, Jetty
>            Reporter: Vamsavardhana Reddy
>             Fix For: 1.2, 1.1.x
>
>         Attachments: GERONIMO-2278.patch
>
>
> Here is what I noticed.
> 1.  Edit page does not show the current values for fields in the select boxes.
> 2.  Changes made to the KeyStore field are not saved.
> 3.  The page does not provide for editing the keyAlias.  keyAlias is 
> hardcoded as "geronimo".  Even if 2 from above is fixed, users are forced to 
> use "geronimo" for the keyAlias.

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

        

Reply via email to