Hello everone,
I have 2 directory to create uses into RSA HRMS and AD. in AD users have different logic for sAMaccountName (due to migrated users from other company)
HRMS for Employee creation and AD for Vendor creation.
I have created different ID to store different userID in the RSA e.g. User ID, Login ID. Also I have done below mapping in the unification for join.
For example in RSA one user has user ID is like RS12345AD and login ID is 12345 and in AD user sAMAccoutname (mapped to user ID in collector) is like 12345
When I collect identities using below join, it is creating new user in RSA, Kindly let me know if I am missing anything.
And is it possible to have multiple join criteria for one collector ?
Note: When I use only 1 join criteria HRMS_IDC.Loign ID = AD Attribute IDC.User Id, it works
Regards,
Pankaj
OK - I would strongly recommend revisiting that as an option if possible. The root cause here is inconsistent AD data so remediating this with a new attribute would be easiest. However….
With regards to the different user types, is there a way to distinguish them easily within your HRMS feed?
If so, you could set up 2 IDC pointing to HRMS. One collecting all staff that will match on Login ID and one that will match on User Id.
If this is an option you would need to be certain that:
Your unification could then match on HRMS_IDC1.Login ID = AD User Id and HRMS_IDC2.User Id = AD User Id