Migrate Keycloak Authorization config classes to the @ConfigMapping
#39603
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
Status for workflow
|
sberyozkin
approved these changes
Mar 21, 2024
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.
Migrates Keycloak Authorization extension config classes to the
@ConfigMapping. This is yet another prestep for #17664 because users shoudl use build to create API (interface) instead of deprecated config classes. The migration aligns with migration of other Security extensions. There are no Quarkiverse extensions https://mvnrepository.com/artifact/io.quarkus/quarkus-keycloak-authorization/usages that are broken by this migration. Right now, users don't need to work with these config classes (didn't find it in reference guide). The PR also changes phase of tenant config which was meant to be done in the #39512.