AMQP 1.0: support JWT (OAuth 2) token renewal #12599
Draft
+411
−55
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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: