Skip to content

OAuth2: support opaque tokens #13978

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 26 commits into
base: main
Choose a base branch
from
Draft

OAuth2: support opaque tokens #13978

wants to merge 26 commits into from

Conversation

MarcialRosales
Copy link
Contributor

@MarcialRosales MarcialRosales commented May 29, 2025

Proposed Changes

Implements #8662

RabbitMQ will never cache the resolved JWT access token. it will only be cached for the duration of the session/connection. Once RabbitMQ resolves the JWT access token (i..e exchanged the opaque one for a JWT one), it will work as usual, i.e. it will use the expiry date in the resolved JWT access token.

Types of Changes

What types of changes does your code introduce to this project?
Put an x in the boxes that apply

  • Bug fix (non-breaking change which fixes issue #NNNN)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause an observable behavior change in existing systems)
  • Documentation improvements (corrections, new content, etc)
  • Cosmetic change (whitespace, formatting, etc)
  • Build system and/or CI
And add client used to introspect tokens
so that it is possible to test with clients configured with opaque tokens and others with jwt tokens
Refactoring needed so that the resolved jwt token is kept in the management ui so that the backend does not need to reoolve it permanentely
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment