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
{{ message }}
This repository has been archived by the owner on Nov 16, 2022. It is now read-only.
When defining a KeycloakAPIAuthenticationFlow on the Realm object there is a property to define the ID. When configuring that and applying the Realm Ressource (not existing prior to that) the Flow is created but the ID is a different one from the configured one.
Sadly that makes overwriting the default flow on a client impossible…
Hi @Robbilie ,
there is no "special treatment" of the id field from the the operator and it's directly translated to a REST API call to Keycloak, can you please verify the raw functionality using the Admin REST API of Keycloak?
yeah sorry forgot to mention that, already tested and it worked as expected, that confused me too…
i didnt see any special treatment either, i dont have a second instance of the operator running though to test if the issue is specific to that instance…
EDIT: POST /auth/admin/realms/testrealm/authentication/flows that api
Describe the bug
When defining a KeycloakAPIAuthenticationFlow on the Realm object there is a property to define the ID. When configuring that and applying the Realm Ressource (not existing prior to that) the Flow is created but the ID is a different one from the configured one.
Sadly that makes overwriting the default flow on a client impossible…
Version
15.1.1
Expected behavior
The Flow in Keycloak has the configured ID.
Actual behavior
The Flow in Keycloak has a newly generated ID.
How to Reproduce?
Apply this yaml and check the x509 flow:
Anything else?
No response
The text was updated successfully, but these errors were encountered: