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
Testing with a password grant (as opposed to the code flow) can be preferred by some users but Dev UI backed up by Dev Services for Keycloak offers a limited support - only those users set in quarkus.keycloak.devservices.users will be recognized - which does not scale at all if a custom realm is imported - not does it really work - who would copy all the users and their passwords from the Keycloak realm into this devservices map property...
It is actually well supported in a Dev UI when the OIDC provider is already started - a password field will be offered and as many users/passwords as required can be tested.
The same should be done with Dev Services for Keycloak - quarkus.keycloak.devservices.users should be restricted to creating the users for the default realm...
Also looks like DevUI for Dev Services for Keycloak misses on the non-devservices related properties changes, ex, client-id - the container does not have to be restarted so the new properties do not propagate to DevUI which needs it to do the code flow redirects etc
Implementation ideas
No response
The text was updated successfully, but these errors were encountered:
Description
Testing with a password grant (as opposed to the code flow) can be preferred by some users but Dev UI backed up by Dev Services for Keycloak offers a limited support - only those users set in
quarkus.keycloak.devservices.users
will be recognized - which does not scale at all if a custom realm is imported - not does it really work - who would copy all the users and their passwords from the Keycloak realm into this devservices map property...It is actually well supported in a Dev UI when the OIDC provider is already started - a password field will be offered and as many users/passwords as required can be tested.
The same should be done with
Dev Services for Keycloak
-quarkus.keycloak.devservices.users
should be restricted to creating the users for the default realm...Also looks like DevUI for
Dev Services for Keycloak
misses on the non-devservices related properties changes, ex,client-id
- the container does not have to be restarted so the new properties do not propagate to DevUI which needs it to do the code flow redirects etcImplementation ideas
No response
The text was updated successfully, but these errors were encountered: