JWT authentication for REST client #40036
Unanswered
IvanPuntev
asked this question in
Q&A
Replies: 2 comments 15 replies
-
/cc @cescoffier (rest-client), @geoand (rest-client), @sberyozkin (jwt) |
Beta Was this translation helpful? Give feedback.
0 replies
-
@IvanPuntev Right, that should do it, the filter will manage the token acquisition and refresh and will set it as the |
Beta Was this translation helpful? Give feedback.
15 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
For jwt authentication in my rest client interface I'm currently using custom class that extends the ReactiveClientHeadersFactory and manually building the access token in it. What is the proper way in quarkus 3 to do that? Is it possible to be as simple as the OIDC - you just add annotation @RegisterProvider(OidcClientRequestReactiveFilter.class) to the rest client and add some config properties?
quarkus.oidc-client.auth-server-url=
quarkus.oidc-client.client-id=
quarkus.oidc-client.credentials.secret=
quarkus.oidc-client.grant.type=
quarkus.oidc-client.discovery-enabled=
quarkus.oidc-client.token-path=
quarkus.oidc-client.grant-options.password.username=
quarkus.oidc-client.grant-options.password.password=
Beta Was this translation helpful? Give feedback.
All reactions