'Account disable test' criteria overridden when using 'Users must be a member of' about redmine_ldap_sync HOT 6 CLOSED

That means that the user is both on the :disabled and on the :enabled list after fetching the users from the ldap.

Are you using the latest commit version of the plugin?

from redmine_ldap_sync.

Yes, this was the latest commit version (0377ede). The LDAP source is Active Directory, using the default AD disable test ("flags.to_i & 2 != 0" on userAccountControl).

from redmine_ldap_sync.

The only way I see that happening is that of existing two users on the LDAP with the same login name.
One locked and a second one unlocked.

Just to clear that hypotheses.
Can you add the following line of code on line 35 of auth_source_ldap_patch.rb, run a sync and tell me if it returns an empy
array -- "[]"?

puts "!!! Users intersection = #{(ldap_users[:disabled] & ldap_users[:enabled]).inspect}"

from redmine_ldap_sync.

Yes, it returned an empty array:

!!! Users intersection = []

from redmine_ldap_sync.

I should also add - I am using nested groups, and I also do not believe those users being locked and then later unlocked are truly disabled. I'm not sure why the disable test may be flagging them, as they aren't disabled in AD.

Unfortunately I've never worked with Ruby before, so I've got a bit of a learning curve to dig in and really troubleshoot further - but will see what I can determine.

from redmine_ldap_sync.

Closing this issue due to the release of version 2.0.
Feel free to reopen if you also have problems on this version.

from redmine_ldap_sync.