Effectively then I mistaken the need thanks for the information. I will create an idea:
A tool to import from an LDAP is not a solution for us. We are a big company with several hundred of thousands users.... with hundreds of users going in and out per day worldwide=> I am not sure that the tool could handle this kind of synchro everyday ?
>>our jira is using full name as identifier as in octane we are using an UID.
i believe you're describing a completely different problem.
if i'm not mistaken, you're looking for an LDAP enabled way to map user representations across products, rather than using LDAP enabled authentication to log into Connect (the subject of this idea)
In any case, you can already do that too.
Use our User Mapping utility to import user representations from LDAP into MF Connect, then turn on User Maps and run your syncs
A big up for the need: our jira is using full name as identifier as in octane we are using an UID. We should be able to use a ldap and point which ldap field to use to convert the users.