You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robbie Gemmell (JIRA)" <qp...@incubator.apache.org> on 2009/08/06 21:59:14 UTC
[jira] Created: (QPID-2032) AddUser operation in the new
UserManagement UI does not MD5 hash the password when connected to pre-0.5
brokers
AddUser operation in the new UserManagement UI does not MD5 hash the password when connected to pre-0.5 brokers
---------------------------------------------------------------------------------------------------------------
Key: QPID-2032
URL: https://issues.apache.org/jira/browse/QPID-2032
Project: Qpid
Issue Type: Bug
Components: Java Management : JMX Console
Affects Versions: 0.6
Reporter: Robbie Gemmell
Assignee: Robbie Gemmell
Priority: Critical
Fix For: 0.6
Older brokers (pre 0.5) require the user password to be presented by the console in MD5 hashed format. This was changed to plain text in 0.5 when the PlainPasswordFilePrincipleDatabase was updated to allow manipulation using the management console. As a result, the console must detect the broker management API version and send the appropriate content when creating users on older brokers. The new UI is currently not doing this (although does when altering the password).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Assigned: (QPID-2032) AddUser operation in the new
UserManagement UI does not MD5 hash the password when connected to pre-0.5
brokers
Posted by "Robbie Gemmell (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell reassigned QPID-2032:
------------------------------------
Assignee: Aidan Skinner (was: Robbie Gemmell)
Hi Aidan, can you review this change please, thanks.
> AddUser operation in the new UserManagement UI does not MD5 hash the password when connected to pre-0.5 brokers
> ---------------------------------------------------------------------------------------------------------------
>
> Key: QPID-2032
> URL: https://issues.apache.org/jira/browse/QPID-2032
> Project: Qpid
> Issue Type: Bug
> Components: Java Management : JMX Console
> Affects Versions: 0.6
> Reporter: Robbie Gemmell
> Assignee: Aidan Skinner
> Priority: Critical
> Fix For: 0.6
>
>
> Older brokers (pre 0.5) require the user password to be presented by the console in MD5 hashed format. This was changed to plain text in 0.5 when the PlainPasswordFilePrincipleDatabase was updated to allow manipulation using the management console. As a result, the console must detect the broker management API version and send the appropriate content when creating users on older brokers. The new UI is currently not doing this (although does when altering the password).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Resolved: (QPID-2032) AddUser operation in the new
UserManagement UI does not MD5 hash the password when connected to pre-0.5
brokers
Posted by "Aidan Skinner (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aidan Skinner resolved QPID-2032.
---------------------------------
Resolution: Fixed
> AddUser operation in the new UserManagement UI does not MD5 hash the password when connected to pre-0.5 brokers
> ---------------------------------------------------------------------------------------------------------------
>
> Key: QPID-2032
> URL: https://issues.apache.org/jira/browse/QPID-2032
> Project: Qpid
> Issue Type: Bug
> Components: Java Management : JMX Console
> Affects Versions: 0.6
> Reporter: Robbie Gemmell
> Assignee: Aidan Skinner
> Priority: Critical
> Fix For: 0.6
>
>
> Older brokers (pre 0.5) require the user password to be presented by the console in MD5 hashed format. This was changed to plain text in 0.5 when the PlainPasswordFilePrincipleDatabase was updated to allow manipulation using the management console. As a result, the console must detect the broker management API version and send the appropriate content when creating users on older brokers. The new UI is currently not doing this (although does when altering the password).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Updated: (QPID-2032) AddUser operation in the new
UserManagement UI does not MD5 hash the password when connected to pre-0.5
brokers
Posted by "Robbie Gemmell (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell updated QPID-2032:
---------------------------------
Status: Ready To Review (was: In Progress)
> AddUser operation in the new UserManagement UI does not MD5 hash the password when connected to pre-0.5 brokers
> ---------------------------------------------------------------------------------------------------------------
>
> Key: QPID-2032
> URL: https://issues.apache.org/jira/browse/QPID-2032
> Project: Qpid
> Issue Type: Bug
> Components: Java Management : JMX Console
> Affects Versions: 0.6
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Priority: Critical
> Fix For: 0.6
>
>
> Older brokers (pre 0.5) require the user password to be presented by the console in MD5 hashed format. This was changed to plain text in 0.5 when the PlainPasswordFilePrincipleDatabase was updated to allow manipulation using the management console. As a result, the console must detect the broker management API version and send the appropriate content when creating users on older brokers. The new UI is currently not doing this (although does when altering the password).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org