You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm working on a token CLI for Keycloak that can be useful for developers to understand tokens and flows, but also that can be used to obtain tokens for other CLIs, including supporting for kubectl.
For password and service accounts I'm using the oidc-client, which is great as it has a lot of features that I would otherwise have to write, but one problem is that it doesn't support Device Authorization Grant.
I'm not expecting oidc-client to do the first leg of obtaining the device code, but would be great if it could support the token request. I suspect this may be as simple as adding DEVICE_CODE("urn:ietf:params:oauth:grant-type:device_code") to
Hi Stian, @stianst, sure, yes, the dynamic parameters can be passed with the map, would you like to open a PR to add that enum value, I can help with adding a simple test ?
@stianst I can do the whole PR a bit later as you already proposed the actual enum value, but of course you are welcome to contribute if you'd like, we can do it for Quarkus 3.9.0
Description
I'm working on a token CLI for Keycloak that can be useful for developers to understand tokens and flows, but also that can be used to obtain tokens for other CLIs, including supporting for kubectl.
For password and service accounts I'm using the
oidc-client
, which is great as it has a lot of features that I would otherwise have to write, but one problem is that it doesn't support Device Authorization Grant.I'm not expecting
oidc-client
to do the first leg of obtaining the device code, but would be great if it could support the token request. I suspect this may be as simple as adding DEVICE_CODE("urn:ietf:params:oauth:grant-type:device_code") toquarkus/extensions/oidc-client/runtime/src/main/java/io/quarkus/oidc/client/OidcClientConfig.java
Line 55 in 053cb7c
Implementation ideas
No response
The text was updated successfully, but these errors were encountered: