4.1.0 release notes updates for beta.5

Author: michaelklishin

release-notes/4.1.0.md

@@ -165,10 +165,38 @@ This section can be incomplete and will be expanded as 4.1 approaches its releas
 
    GitHub issue: [#10519](https://github.com/rabbitmq/rabbitmq-server/issues/10519), [#12564](https://github.com/rabbitmq/rabbitmq-server/pull/12564)
 
+ * AMQP 1.0 and AMQP 0-9-1 connections now dynamically adjust their TCP socket buffers.
+
+
+
+   GitHub issue: [#13363](https://github.com/rabbitmq/rabbitmq-server/pull/13363)
+
  * Peer discovery resilience improvements.
 
    GitHub issues: [#12801](https://github.com/rabbitmq/rabbitmq-server/pull/12801), [#12809](https://github.com/rabbitmq/rabbitmq-server/pull/12809)
 
+ * AMQP 1.0 and AMQP 0-9-1 connections now produce more specific error messages when an incorrect data is sent
+   by the client during connection negotiation.
+
+   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.
+
+   GitHub issue: [#13559](https://github.com/rabbitmq/rabbitmq-server/pull/13559)
+
+ * AMQP 0-9-1 and AMQP 1.0 connections now use a higher pre-authentication maximum allowed frame limit size by default.
+   This means that [larger JWT tokens can be accepted](https://www.rabbitmq.com/docs/troubleshooting-oauth2) without any configuration.
+
+   GitHub issue: [#13542](https://github.com/rabbitmq/rabbitmq-server/pull/13542)
+
+ * Plugins now can mark queues and streams as protected from deletion by applications.
+
+   GitHub issue: [#13525](https://github.com/rabbitmq/rabbitmq-server/pull/13525)
+
+ * Internal API changes needed by a future version of the [message deduplication plugin](https://github.com/noxdafox/rabbitmq-message-deduplication).
+
+   Contributed by @noxdafox.
+
+   GitHub issue: [#13374](https://github.com/rabbitmq/rabbitmq-server/pull/13374)
+
 #### Bug Fixes
 
  * AMQP 0-9-1 channel exception generator could not handle entity names (say, queue or stream names)
@@ -265,6 +293,22 @@ This section can be incomplete and will be expanded as 4.1 approaches its releas
 
    GitHub repository: [`rabbitmq/rabbitmqadmin-ng`](https://github.com/rabbitmq/rabbitmqadmin-ng)
 
+ * New health check for detecting quorum queues without an elected leader.
+
+   ```shell
+   # across all virtual host
+   rabbitmq-diagnostics check_for_quorum_queues_without_an_elected_leader --across-all-vhosts "^name.pattern.*"
+   ```
+
+   ```shell
+   # in a specific virtual host
+   rabbitmq-diagnostics check_for_quorum_queues_without_an_elected_leader --vhost "vhost-1" "^name.pattern.*"
+   ```
+
+   Contributed by @Ayanda-D.
+
+   GitHub issue: [#13487](https://github.com/rabbitmq/rabbitmq-server/pull/13487)
+
  * `rabbitmq-diagnostics check_if_any_deprecated_features_are_used` implementation is now more complete
    (checks for a more deprecated features).
 
@@ -353,6 +397,24 @@ This section can be incomplete and will be expanded as 4.1 approaches its releas
 
    GitHub issue: [#12643](https://github.com/rabbitmq/rabbitmq-server/pull/12643)
 
+ * The HTTP API and management UI now can use a [separate chain of authentication and authorization backends](https://www.rabbitmq.com/docs/access-control).
+
+   This means that a separate list of backends can now be used for the messaging protocol clients and the HTTP API access.
+
+   Contributed by @aaron-seo.
+
+   GitHub issue: [#13465](https://github.com/rabbitmq/rabbitmq-server/pull/13465)
+
+ * The UI now provides a dark theme.
+
+   Contributed by @efimov90.
+
+   GitHub issues: [#13545](https://github.com/rabbitmq/rabbitmq-server/pull/13545), [#3478](https://github.com/rabbitmq/rabbitmq-server/issues/3478)
+
+ * Web app tab title now changes depending on the selected top-level tab.
+
+   GitHub issue: [#13512](https://github.com/rabbitmq/rabbitmq-server/pull/13512)
+
 #### Bug Fixes
 
  * Fixes a false positive that incorrectly reported deprecated feature use, specifically
@@ -401,6 +463,10 @@ This section can be incomplete and will be expanded as 4.1 approaches its releas
 
    GitHub issue: [#12210](https://github.com/rabbitmq/rabbitmq-server/issues/12210)
 
+ * Support for more complex JWT token structures, such as those sometimes used by Keycloak.
+
+   GitHub issue: [#12324](https://github.com/rabbitmq/rabbitmq-server/issues/12324), [#13216](https://github.com/rabbitmq/rabbitmq-server/pull/13216)
+
  * [OpenID Discovery Endpoint](https://openid.net/specs/openid-connect-discovery-1_0.html#ProviderConfigurationRequest) now can be configured. This is particularly relevant for
    Azure Entra (né Azure AD) users.
 
@@ -435,6 +501,10 @@ This section can be incomplete and will be expanded as 4.1 approaches its releas
 
    GitHub issue: [#12888](https://github.com/rabbitmq/rabbitmq-server/pull/12888)
 
+ * The shutdown sequence of Shovel connections and AMQP 1.0 sessions is now safer.
+
+   GitHub issue: [#2596](https://github.com/rabbitmq/rabbitmq-server/issues/2596)
+
 
 ### Event Exchange Plugin