Feature: Support for authorizing clientId values based on userId - #2461
Open
mattrpav wants to merge 2 commits into
Open
Feature: Support for authorizing clientId values based on userId#2461mattrpav wants to merge 2 commits into
mattrpav wants to merge 2 commits into
Conversation
mattrpav
changed the title
mattrpav
force-pushed
the
amq-authenticate-clientid
branch
from
September 7, 2026 20:40
e79af2f to
18e2734
Compare
mattrpav
changed the title
mattrpav
force-pushed
the
amq-authenticate-clientid
branch
from
September 7, 2026 20:43
18e2734 to
083533e
Compare
- Includes support for clientId as a network connection authorization
mattrpav
force-pushed
the
amq-authenticate-clientid
branch
from
September 7, 2026 21:07
083533e to
da71780
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This feature provides hooks for authorization connections based on clientId, including specifying if a specific user may register their connection as a network connection.
Network Connection authorization is optional, and detected automatically by the broker-side JAAS handling when a clientId authorization is configured. If clientId authorization is not configure, the authorization check for network connections is skipped matching current behavior.