AMQP 1.0: support JWT (OAuth 2) token renewal #12599
Draft
+411
−55
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ansd
force-pushed
the
amqp-token-renew
branch
2 times, most recently
from
d2888ae
to
88fad63
Compare
michaelklishin
changed the title
ansd
force-pushed
the
amqp-token-renew
branch
2 times, most recently
from
41d24ab
to
eff36e1
Compare
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. TODOs: * Check new log process metadata * Update docs
ansd
force-pushed
the
amqp-token-renew
branch
from
eff36e1
to
9e372db
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
PUTa new token on HTTP API v2 path/auth/tokens. RabbitMQ will then: