You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* AMQP 1.0 and AMQP 0-9-1 connections now produce more specific error messages when an incorrect data is sent
179
+
by the client during connection negotiation.
180
+
181
+
For example, when a [TLS-enabled](https://www.rabbitmq.com/docs/ssl) client connects to a non-TLS port, or an HTTP GET request is sent to the AMQP port.
* Internal API changes needed by a future version of the [message deduplication plugin](https://github.com/noxdafox/rabbitmq-message-deduplication).
* The HTTP API and management UI now can use a [separate chain of authentication and authorization backends](https://www.rabbitmq.com/docs/access-control).
401
+
402
+
This means that a separate list of backends can now be used for the messaging protocol clients and the HTTP API access.
*[OpenID Discovery Endpoint](https://openid.net/specs/openid-connect-discovery-1_0.html#ProviderConfigurationRequest) now can be configured. This is particularly relevant for
405
471
Azure Entra (né Azure AD) users.
406
472
@@ -435,6 +501,10 @@ This section can be incomplete and will be expanded as 4.1 approaches its releas
0 commit comments