[
https://issues.apache.org/jira/browse/QPID-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Gemmell updated QPID-1537:
---------------------------------
Attachment: QPID-1537_18feb2009.patch
I attach QPID-1537_18feb2009.patch, which reinstates the MBean versioning
previously added and removed. This is required for backwards compatibility in
light of changes to the principal databses to make the PlainPD manipulatable
and cached, and make the B64MD5PD take plain text input. Forwards compatibility
issues with older consoles has been addressed by QPID-1511, as the addition of
authentication to the RMI connector prevents them connecting.
The patch is largely identical to the previous changes, with one alteration
made to catch single-instance MBeans, which get their key properties from a
different method than the other MBeans and so were not versioned by the
previous changes.
> Version the MBeans so we can maintain backward compatibility with new features
> ------------------------------------------------------------------------------
>
> Key: QPID-1537
> URL: https://issues.apache.org/jira/browse/QPID-1537
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Affects Versions: M2, M2.1, M3, M4
> Reporter: Martin Ritchie
> Attachments: QPID-1537_18feb2009.patch
>
>
> Summary:
> With the change to the UserManagementMBean to change the ensure that the
> input is always plain text for the password we need to ensure we can still
> send the hashed version with the older versions of the broker.
> Setting a version flag on the MBean will allow us to tell when to send what
> value. It will also allow us to handle future changes.
--
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:[email protected]
