You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org> on 2007/04/25 12:42:15 UTC
[jira] Created: (QPID-473) Base64MD5PrincipalDatabase doesn't check
password changes were applied to disk before storing in memory
Base64MD5PrincipalDatabase doesn't check password changes were applied to disk before storing in memory
-------------------------------------------------------------------------------------------------------
Key: QPID-473
URL: https://issues.apache.org/jira/browse/QPID-473
Project: Qpid
Issue Type: Bug
Components: Java Broker
Reporter: Martin Ritchie
Assigned To: Martin Ritchie
Fix For: M2
When using the JMX console to set a password the B64MD5PFPD updates the internal map of users but when the write fails it doesn't revoke the users access.
While when the jmxremote.access update fails then it will report opperation unsucessful but will have created the login as the PFPD doesn't revoke the permissions.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (QPID-473) Base64MD5PrincipalDatabase doesn't
check password changes were applied to disk before storing in memory
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie resolved QPID-473.
---------------------------------
Resolution: Fixed
> Base64MD5PrincipalDatabase doesn't check password changes were applied to disk before storing in memory
> -------------------------------------------------------------------------------------------------------
>
> Key: QPID-473
> URL: https://issues.apache.org/jira/browse/QPID-473
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Reporter: Martin Ritchie
> Assigned To: Martin Ritchie
> Fix For: M2
>
>
> When using the JMX console to set a password the B64MD5PFPD updates the internal map of users but when the write fails it doesn't revoke the users access.
> While when the jmxremote.access update fails then it will report opperation unsucessful but will have created the login as the PFPD doesn't revoke the permissions.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.