Skip to content
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

Idempotency problem with ldap user provider #314

Open
Xaraxia opened this issue Jun 19, 2024 · 2 comments
Open

Idempotency problem with ldap user provider #314

Xaraxia opened this issue Jun 19, 2024 · 2 comments

Comments

@Xaraxia
Copy link

Xaraxia commented Jun 19, 2024

Notice: /Stage[main]/Profile::Keycloak/Keycloak_ldap_user_provider[AD on REDACTED]/user_object_classes: current_value person, organizationalPerson, user, should be person, organizationalPerson, user (noop) (corrective)

Running a noop, you can see the above ... it seems to be trying to change it unnecessarily.

@treydock
Copy link
Owner

Can you share how you are defining user_object_classes? From that output it looks like you may have:

user_object_classes => ['person', 'organizationalPerson', 'user'],

I updated the acceptance tests which check for idempotency and saw this on first run:

  Notice: /Stage[main]/Main/Keycloak_ldap_user_provider[LDAP]/user_object_classes: user_object_classes changed inetOrgPerson,organizationalPerson to person,organizationalPerson,user

Then second run had no changes. What version of this module are you using and what version of Keycloak?

Was there any other output related to that LDAP user provider?

@treydock
Copy link
Owner

Also can you share this output from the Keycloak server where happened? Example:

# /opt/keycloak/bin/kcadm-wrapper.sh get components -r <realm name> | jq '.[] | select(.name == "AD") | .config.userObjectClasses'
Logging into http://localhost:8080/ as user admin of realm master

[
  "posixAccount"
]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants