Versions Compared

Old Version 22

changes.mady.by.user keith wall

Saved on

compared with

New Version 23

changes.mady.by.user keith wall

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Management features
    1. Support for configured object queries using JMS selector style expressions – allows an operator to better understand a Broker's operation (e.g. show me queue depths for all queues on this virtualhost).
    2. Web Management Console extension to allow queries to be edited/saved/retrieved and simple dashboards (comprising one or more saved queries)
    3. Ability to persist user-preferences at the Broker and Virtualhost level (for replication within a HA group)
  2. Authentication / Access Control
    1. Support for LDAP Groups (QPID-7116)
    2. Allow ACLs to be applied at Virtualhost level (for replication within a HA group)
    3. Caching of authentication results to reduce load on back end authentication providers (such as an LDAP Open Directory)
  3. Web Management Console
    1. Implement UIs for End to End Encryption (QPID-7037/QPID-7036), OAuth2 ( QPID-7112 / QPID-7111 ) and Virtual Host Aliases (QPID-7110)
    2. Improve UI performance when monitoring large deployments.
  4. TLS Cipher suite ordering in order to make use of faster ciphers available JDK 1.8 (QPID-7113)

...

  1. Extension to allow easy deployment of Brokers in 'common configurations profiles'
    1. This will allow a user to define one or more common configuration profiles used at deployment time to ensure that many Brokers are deployed in the same way to the same standard
    2. It is envisaged that this feature will be used to define 'hardened profiles' such as an "LDAP with TLS transport for messaging/management".
    3. This might involve some kind of manual configuration interrogation during first run ('give me your path to TLS cert' etc) and options  to integrate with systems such as Puppet.
  2. Access Control
    1. New access control provider whose rules are associated with the configured objects themselves.
    2. UI fo the new access control provider.
    3. Define at a metalevel how permissions 'role-up' for instance a user with permission to consume and publish to queue might be consider to automatically have the move message permission,
    4. Define how permissions inherit 
  3. Make user identity unique (QPID-7092)
  4. Gracefully close TLS connections (QPID-6991)
  5. Improve verification of the recipient's certificate used for Message Encryption (QPID-7309)
  6. Impose absolute time limit on the WMC session 

 

...

Release v7.x

(2017)

Qpid Broker for Java

...