You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Joe Bohn (JIRA)" <de...@geronimo.apache.org> on 2006/07/27 21:03:13 UTC
[jira] Created: (GERONIMO-2236) keystore portlet - providing a null
or incorrect password on edit unlock cannot be recovered
keystore portlet - providing a null or incorrect password on edit unlock cannot be recovered
--------------------------------------------------------------------------------------------
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.1.1, 1.2
Environment: windows xp
tomcat or jetty
Reporter: Joe Bohn
Fix For: 1.1.1, 1.2
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
[jira] Updated: (GERONIMO-2236) keystore portlet - providing a null
or incorrect password on edit unlock can only be recovered with server
recycle
Posted by "Joe Bohn (JIRA)" <de...@geronimo.apache.org>.
[ 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
[jira] Assigned: (GERONIMO-2236) keystore portlet - providing a
null or incorrect password on edit unlock can only be recovered with server
recycle
Posted by "Vamsavardhana Reddy (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2236?page=all ]
Vamsavardhana Reddy reassigned GERONIMO-2236:
---------------------------------------------
Assignee: Vamsavardhana Reddy
> 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.1.1, 1.2, 1.1
> Environment: windows xp
> tomcat or jetty
> Reporter: Joe Bohn
> Assigned To: Vamsavardhana Reddy
> Fix For: 1.2, 1.1.x
>
>
> 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
[jira] Closed: (GERONIMO-2236) keystore portlet - providing a null
or incorrect password on edit unlock can only be recovered with server
recycle
Posted by "Vamsavardhana Reddy (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2236?page=all ]
Vamsavardhana Reddy closed GERONIMO-2236.
-----------------------------------------
Resolution: Fixed
This was partly fixed in rev 465702, fix for GERONIMO-2504, and a PortletException is thrown if a wrong passord is provided.
This update handles the exception and displays error message or info message in the cosole depending on the success of unlock.
Fixed in rev 477131 (branches\1.2) and rev 477134 (trunk).
> 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
> Assigned To: Vamsavardhana Reddy
> Fix For: 1.2, 2.0
>
>
> 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
[jira] Updated: (GERONIMO-2236) keystore portlet - providing a null
or incorrect password on edit unlock can only be recovered with server
recycle
Posted by "Joe Bohn (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2236?page=all ]
Joe Bohn updated GERONIMO-2236:
-------------------------------
Fix Version/s: 1.1.x
(was: 1.1.1)
This is annoying but not a critical issue for 1.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.x
>
>
> 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
[jira] Updated: (GERONIMO-2236) keystore portlet - providing a null
or incorrect password on edit unlock can only be recovered with server
recycle
Posted by "Vamsavardhana Reddy (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2236?page=all ]
Vamsavardhana Reddy updated GERONIMO-2236:
------------------------------------------
Fix Version/s: 2.0
(was: 1.1.x)
> 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
> Assigned To: Vamsavardhana Reddy
> Fix For: 1.2, 2.0
>
>
> 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