Closes #9259. ## What? Allow an AMQP 1.0 client to renew an OAuth 2.0 token before it expires. ## Why? This allows clients to keep the AMQP connection open instead of having to create a new connection whenever the token expires. ## How? As explained in #9259 (comment) the client can `PUT` a new token on HTTP API v2 path `/auth/tokens`. RabbitMQ will then: 1. Store the new token on the given connection. 2. Recheck access to the connection's vhost. 3. Clear all permission caches in the AMQP sessions. 4. Recheck write permissions to exchanges for links publishing to RabbitMQ, and recheck read permissions from queues for links consuming from RabbitMQ. The latter complies with the user expectation in #11364.

AMQP 1.0: support JWT (OAuth 2) token renewal#12599michaelklishin merged 1 commit intomainrabbitmq/rabbitmq-server:mainfrom amqp-token-renewrabbitmq/rabbitmq-server:amqp-token-renewCopy head branch name to clipboard

Commits

Commits on Oct 30, 2024

Support AMQP 1.0 token renewal

AMQP 1.0: support JWT (OAuth 2) token renewal#12599
michaelklishin merged 1 commit intomainfrom
amqp-token-renew