-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ldap Provider Issue on secondary Realm #317
Comments
Could you provide the Puppet or YAML code you're using to define the LDAP user provider? Can redact any sensitive information. |
Hi @treydock I think the problem is located here:
This line returns all (!) realms instead of just the one requested with -r :
And at this line always the last realm in the array returned is set as
To get the
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
thanks for the great module.
While setting up new Instances with newest module on Ubuntu 22.04 we noticed probably a bug or missing config Option for the ldap providers.
Maybe we have not seen the correct parameter, but it seems we cannot set the parent_id for the keycloak_ldap_user_provider, only realm.
What happens is that puppet says its all fine and actually creates the ldap connections without issue, but in the DB we can see the LDAPs being linked to master realm on parent_Id and to the realm that specified as parameter.
Sadly they dont show up on the gui at all, neither in master nor secondary realm.
Is there a way to specify the parent_id for the keycloak_ldap_user_provider or is that a missing parameter?
Kind regards,
Mathias
The text was updated successfully, but these errors were encountered: