Migrate Security WebAuth config classes to @ConfigMapping #39357
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.
We try to migrate config classes to interfaces those of the OIDC-related extensions where it shouldn't break thing (we are not aware of reasons why users should inject migrated config classes or of Quarkiverse extensions that use that extension). That effort is tracked here #39185.
I mentioned when going through security-related extensions that WebAuth should fit this criteria https://mvnrepository.com/artifact/io.quarkus/quarkus-security-webauthn/usages. I don't see config classes mentioned in https://quarkus.io/guides/security-webauthn nor I can see user-defined beans that should inject it in most cases. Hence I propose to also migrate Security WebAuth for reasons discusses in the related above-mentioned issue.