Closed argenstijn closed 1 month ago
/cc @pedroigor (oidc), @sberyozkin (oidc)
@argenstijn
When you use @RegisterProvider
it is done at the REST client level to which OidcClientRequestReactiveFilter.class
means only that it is just some provider class, it does not know anything about OIDC client or if the feature is disabled.
@OidcClient
is managed directly at the OIDC client build steps level which is only activated if the OIDC client feature is enabled.
We can probably add a check at the filter level to avoid NPEs
Describe the bug
While testing you can disabled the oidc client by setting quarkus.oidc-client.enabled to false. This work perfectly in combination with @OidcClientFilter. But not when you are using @RegisterProvider using the default class or custom class.
Expected behavior
oidc Client is disabled when using @RegisterProvider
Actual behavior
How to Reproduce?
Output of
uname -a
orver
Microsoft Windows [Version 10.0.19045.4529]
Output of
java -version
openjdk 21.0.2 2024-01-16 LTS OpenJDK Runtime Environment Corretto-21.0.2.13.1 (build 21.0.2+13-LTS) OpenJDK 64-Bit Server VM Corretto-21.0.2.13.1 (build 21.0.2+13-LTS, mixed mode, sharing)
Quarkus version or git rev
3.12.2
Build tool (ie. output of
mvnw --version
orgradlew --version
)3.9.6
Additional information
No response