Hey ivrilider611076,
For your version the highest you can go according to the compatibility check show is 1.0.9
To simply put how the Ldapsync work is that base on your configuration, it will connect to the LDAP server and the AD group you specified. Any user within that AD group will get a account created within AE (and whatever client you specified) if they don't have it already.
For example in my own system a while back...
I had done so for Client 100 and it pull the list of user within AD ldap group "TEST.Support.NA"
In the manual it had an example such as this:
<GroupMappings> <map ae="QA" ldap="g1" /> </GroupMappings>
This just mean that in the AE its map to a usergroup call QA and its pulling info from the ldapserver group "g1"
The link to the manual to set up the LDAPsync and its Client setting can be found here:
Configuring LDAP Sync
Configuring Client Settings
This show the synchronization rules and different scenario/example
I don't work nor have access to the AD side, so I can't say what that AD department column would equate to. But base on Ldapsync, it look mainly at the ldpa usergroup level. Hopefully that give you some direction to go on, between example/link to the manual
@AWA Community Member - If someone has used ldapsync + fimailar with the AD side, can you confirm ivrilider611076 questions?