[ELYEE-73] Add a mechanism so that the Jakarta Authorization integration can register itself.#70
Merged
darranl merged 1 commit intowildfly-security:3.xfrom Sep 13, 2025
Merged
Conversation
…ion can register itself.
darranl
changed the title
ivassile
approved these changes
Sep 12, 2025
rsearls
approved these changes
Sep 12, 2025
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
3 participants
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.
https://issues.redhat.com/browse/ELYEE-73
This PR has been simplified to just support registration for Jakarta Authorization. This new class is no-op in the 3,x branch but the expectation is this will contain initialisation logic in the 4.x branch meaning the subsystem can call it in all situations.