11-25-2022 11:10 PM
Hi Team,
Is there any way to pass managerDN of a user from one domain to other domain while provisioning account to Active Directory.
Example
Consider there are two domains Domain1 - > abc.domain.one and Domain2 -> xyz.domain.two
Manager is present in abc.domain.one and his accountID (User DN)is
"Fname, Lname dc=abc, dc=domain, dc=one"
I am provisioning a user into domain2 xyz.domain.two and mapping manager as "Fname, Lname" (Fname, Lname dc=abc, dc=domain, dc=one) from domain 1 abc.domain.one
In CREATEACCOUNTJSON below syntax is used for manager field as
"manager": "${managerAccount==null?'':managerAccount.accountID}"
After provisioning account is getting created in Active Directory but manager field in AD is empty. But manager has to be mapped in Active Directory.
Please share your thoughts to fix this issue. @rushikeshvartak @uthra_rahul @arjungadgul
Thanks,
Harish
11-26-2022 10:08 PM
After provisioning account is getting created in Active Directory but manager field in AD is empty. But manager has to be mapped in Active Directory.
can you elaborate
11-27-2022 06:35 PM
@rushikeshvartak- I am provisioning a user into domain2 xyz.domain.two and assigned manager who is present in domain one "Fname, Lname" (Fname, Lname dc=abc, dc=domain, dc=one) and i used below syntax to assign manager
"manager": "${managerAccount==null?'':managerAccount.accountID}"
But manager is not getting assigned to the user.
Thanks,
Harish
11-27-2022 07:29 PM
Does existing users are assigned similar like this situations ?
are you able to add in AD directly?
11-27-2022 08:35 PM
@rushikeshvartak- This is our new use case where manager from one domain needs to assign to the user who is present in another domain.
11-27-2022 09:51 PM
This is not feasible per AD Restrictions
11-28-2022 02:10 AM
The manager attribute is a DN of the user from the same domain. It will not accept a DN from another domain. Can you validate if you can do this natively in AD ?