Loading...

XML

Word

Printable

Affects:

Release Notes
Release Note Text:

Hide
By default, even with `authenticatePeer: no`, previous versions of the router were offering all available SASL mechanisms to clients (unless saslMechanisms was set explicitly)
This meant that if GSS mechanisms were enabled on the host for other purposes, but not configured for the router, they would be preferred over the less secure ANONYMOUS mechanism and fail.
In the current release, only ANONYMOUS is offered when setting `authenticatePeer: no` and any client can connect anonymously.

Show
By default, even with `authenticatePeer: no`, previous versions of the router were offering all available SASL mechanisms to clients (unless saslMechanisms was set explicitly) This meant that if GSS mechanisms were enabled on the host for other purposes, but not configured for the router, they would be preferred over the less secure ANONYMOUS mechanism and fail. In the current release, only ANONYMOUS is offered when setting `authenticatePeer: no` and any client can connect anonymously.
Release Note Status:
Documented as Resolved Issue
Target Release:

1.0.0.GA

Management tools (qdstat and qdmanage) apparently fail if one has Kerberos set up on the same machine. This was reported upstream as DISPATCH-224.