Saviynt unveils its cutting-edge Intelligence Suite products to revolutionize Identity Security!
Click HERE to see how Saviynt Intelligence is transforming the industry.
Saviynt Copilot Icon

UserUpdateJSON in AD Connector not working - need working examples

Community_User
Saviynt Employee
Saviynt Employee
Originally posted on May 21 2020 at 17:12 UTC

I tried the following UserUpdateJSON in my AD Connector but it is not updating my user object from the AccountImport.


{ "mail": "${user.email}", "telephoneNumber": "${user.phonenumber}" }


Can anyone give me examples of a working JSON?

This message was previously posted on Saviynt's legacy forum by a community user and has been moved over to this forum for continued exposure.
5 REPLIES 5

Community_User
Saviynt Employee
Saviynt Employee
Originally posted on May 22 2020 at 04:26 UTC

Hi Anand,


Greetings!!


I am not sure, what are you trying to achieve.

did you mean "UPDATEUSERJSON" which is at connector level.

If yes, it doesn't has any role in Account Import.

To update your users in Saviynt (if AD is the Authoritative source for User Identities in SSM), you could have "USER_ATTRIBUTE" defined with mappings.

In case, you want to update Accounts at AD end, (If AD is your Target Application), you could specify "UPDATEACCOUNTJSON" and pass on your mappings accordingly.


Thanks & Regards,

Anand Kumar Jha

This message was previously posted on Saviynt's legacy forum by a community user and has been moved over to this forum for continued exposure.

Community_User
Saviynt Employee
Saviynt Employee
Originally posted on May 22 2020 at 15:54 UTC

Hello Anand,


Yes, I am trying to use the UPDATEUSERJSON in the AD Connector.

AD is not my source of record for user identities.


I have a User import running from my HR system.

I have Active Directory configured as an Application, using the AD Connector.


I want to update the Email field from AD to the Email field of the User object.


I thought that if I configure the UPDATEUSERJSON in my AD connection, it will update the user when AD Import job runs.

If that is not the case, do let me know how I can achieve my objective.


Anand Shah

This message was previously posted on Saviynt's legacy forum by a community user and has been moved over to this forum for continued exposure.

Community_User
Saviynt Employee
Saviynt Employee
Originally posted on May 26 2020 at 14:32 UTC

This can be achieved via User import. You could configure related mapping in User_Attribute and post import, you would be able to witness changes in your User attributes. To make sure, this will be an additional usersource for you and you should bring only those attributes along with username what you want to update. Thanks and Regards, Anand Kumar Jha
This message was previously posted on Saviynt's legacy forum by a community user and has been moved over to this forum for continued exposure.

Community_User
Saviynt Employee
Saviynt Employee
Originally posted on May 26 2020 at 17:59 UTC

Hi,


I am trying to use the below createAccountJSON But userPrincipleName and homeDirectory path is not creating in target AD. Could you please tell me the issue in below JSON.


{

"sAMAccountName": "${task.accountName}",

"givenName": "${user.firstname}",

"sn": "${user.lastname}",

"uid": "${user.username}",

"cn": "${user.displayname}",

"userPrincipalName":"${user.username}@test.com",

"homeDirectory": "\\test.com\\dfs\users\HomeDirectorie\\${user.username}",

"objectclass": [

"top",

"person",

"organizationalPerson",

"user"

]

}

This message was previously posted on Saviynt's legacy forum by a community user and has been moved over to this forum for continued exposure.

Community_User
Saviynt Employee
Saviynt Employee
Originally posted on May 27 2020 at 04:11 UTC

Hi Suneel,


Greetings!!


Please create a new thread for your query.

We make sure that different queries should be captured in separate threads, so that it could be a reference for other users as well.

We will definitely help you with the appropriate resolution.

Also please include version detail and error information (if any ) you faced during provisioning.


Thanks & Regards,

Anand Kumar Jha

This message was previously posted on Saviynt's legacy forum by a community user and has been moved over to this forum for continued exposure.