Click HERE to see how Saviynt Intelligence is transforming the industry. |
04/30/2024 10:46 PM - last edited on 05/01/2024 07:41 AM by Dave
Hi @rushikeshvartak , is this supported for the AD connector?
I have the similar situation as this post where we are creating update account tasks using actionable analytics, however, we aren't able to update the Service Account Owner in AD.
I have used the same - requestAccessAttributes.get('USEROWNERKEYADDED') but this didn't worked.
Any idea how to achieve this?
[This post has been edited by a Moderator to move to its own thread.]
Solved! Go to Solution.
05/01/2024 08:52 AM
@mahafujkhan1: Did you update Azure Account SiteID to respective User attribute? Like mentioned in this thread: https://forums.saviynt.com/t5/identity-governance/creating-account-service-account-in-azure-ad-with-...
If so then use
${requestAccessAttributes.get('USEROWNERKEYADDED').collect{it.<User column to which you mapped the SiteID>}.join(',')}
05/01/2024 02:50 PM
Could you kindly provide a detailed snapshot of the information extracted from the logs, encompassing errors and other pertinent functionality details encountered during the execution of this process? Your assistance in furnishing this information would greatly aid in the analysis and resolution of any issues .
05/01/2024 03:19 PM
Hi @rushikeshvartak , @Saathvik ,Thank you both for your response on this. @Saathvik I was trying this for AD Connector. I am able to achieve the required outcome with the below configuration
This is UPDATEACCOUNTJSON. So, the ServiceAccountOwnerMap variable is exposed to UPDATEACCOUNTJSON. The only difference I find when we are using the same variable to create an account, we have to fetch the owner details like below