geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joe Bohn (JIRA)" <...@geronimo.apache.org>
Subject [jira] Updated: (GERONIMO-2236) keystore portlet - providing a null or incorrect password on edit unlock can only be recovered with server recycle
Date Thu, 27 Jul 2006 19:03:15 GMT
     [ http://issues.apache.org/jira/browse/GERONIMO-2236?page=all ]

Joe Bohn updated GERONIMO-2236:
-------------------------------

              Summary: keystore portlet - providing a null or incorrect password on edit unlock
can only be recovered with server recycle  (was: keystore portlet - providing a null or incorrect
password on edit unlock cannot be recovered)
    Affects Version/s: 1.1

> keystore portlet - providing a null or incorrect password on edit unlock can only be
recovered with server recycle
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: GERONIMO-2236
>                 URL: http://issues.apache.org/jira/browse/GERONIMO-2236
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: console
>    Affects Versions: 1.2, 1.1, 1.1.1
>         Environment: windows xp
> tomcat or jetty
>            Reporter: Joe Bohn
>             Fix For: 1.2, 1.1.1
>
>
> Providing an incorrect or null password when attempting to unlock a keystore for edit
creates a situation where the keystore appears to be in edit mode but does not show existing
credentials (although new credentials can be created).  Even if the keystore is locked and
then subsequently unlocked for edit using the correct password, the credentials are never
again shown for that "run of the server".   Recovery requires a server recycle.   After the
server recycle the original set of credentials plus any created from the previous run (when
the edit mode was entered with the wrong password) are displayed. 

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

        

Mime
View raw message