The LDAP integration is created for purpose of not requiring to pre-populate OneDev with your LDAP users. Any reason you need to do this?

Thank you for the speedy response.

Part of the migration requires me to pull in all the group and user permissions for all of our projects from our old repository. I cant pull in those permissions until i have all the user accounts created on onedev. There are a substantial number of users, the majority of them haven't logged into the POC onedev instance we have setup ( i would've done it myself but i don't have all the required passwords ).

Most of the devs are still on leave, so i cant get them to log in and create their accounts at this moment. To make the transition easier, I would like to complete the migration before they return.

Will a failed log in attempt, with an existing ldap user create the account or does the authentication need to succeed in order for that to happen?

Upon reflection, we've decided to change our approach with how we handle user permissions. This thread can be considered resolved.

Thank you !

The standard approach to set up permssions for LDAP managed users is to create appropriate groups at LDAP side, and add users to them. Then create same group at OneDev side and assign apporpriate permission to the group.

Anyway, let me know if you encounter any issues along the path.