Adam Reece

Yes, that should be very possible. `userFilter` is just passed across, so if you're not getting any results use the very verbose option `-vv` to potentially see why, or try...

That sounds like a certificate chain trust issue, which is external to this tool. (This uses trust from your system's cryptographic framework.) Common causes are self signed certificates untrusted by...

That came from a change to the Gitlab API only allowing us to set the public email address of an account that is already verified, which is quite silly. Related:...

That's an incredibly strange quirk of the Gitlab platform... I'm not in a position to test this right now but you may want to edit `src/LdapSyncCommand.php` and change "public_email" to...

That is also external to this tool. Searching for "LDAP blocked users cannot be modified by the API" brings up this which may be of use: https://stackoverflow.com/questions/40990190/how-do-i-unblock-ldap-users-in-gitlab-ce

There's limited knowledge this tool can provide on that as the 403 error is returned by the Gitlab API. You may get more information by increasing verbosity (`-vv`), otherwise you'd...

Looks like we have confirmation that for creating users changing the key "public_email" to "email" works. https://github.com/Adambean/gitlab-ce-ldap-sync/issues/27#issuecomment-1077427013

It sounds very sensible to swap the order of these tasks, though there was a different problem raised when attempting to change their email address: https://github.com/Adambean/gitlab-ce-ldap-sync/issues/21

I'm pretty sure that @beharbunjaku implemented this in commit da977aa8007b84c194e6ed43857569641220fd46.

Hi @yasenv-code, do you believe this is still an issue, or did the commit da977aa8007b84c194e6ed43857569641220fd46 resolve this for you?