We are delighted to share our new EIC Delivery Methodology for efficiently managing Saviynt Implementations and delivering quick time to value. CLICK HERE.

manageBy and description field not populating after upgrade to 24.1

tmschiller
New Contributor III
New Contributor III

We recently upgraded our DEV environment for 23.9 to 24.1 and now our service accounts are not provisioning to AD. We've been able to determine the cause is from two lines in our CREATEACCOUNTJSON as follows:

"description": "${String description = 'System User / Upd by SSM / Owner: '; for (def u : ServiceAccountOwnerMap.get('USEROWNERS').get('1')) description += u.lastname + ", " + u.firstname + " [" + u.systemUserName + "], "; return description.substring(0, description.length()-2);}",

"manager": "${ServiceAccountOwnerMap.get('USEROWNERS').get('1')?.get(0)?.customproperty34}",

We changed each line to the code shown below and made a new request using an owner that is an active user in Saviynt, has a firstname, lastname, and username and the customproperty34 on the user is the distinguishedName. The account provisions, but the manageBy is blank and the description provisions with only "System User / Upd by SSM / Owner: "

"description": "${String description = 'System User / Upd by SSM / Owner: '; for (def u : ServiceAccountOwnerMap.USEROWNERS.get('1')) description += u.lastname + ", " + u.firstname + " [" + u.systemUserName + "], "; return description.substring(0, description.length()-2);}",

"manager": "${ServiceAccountOwnerMap.USEROWNERS.get('1').collect{it.customproperty34.toString()}[0]}",

We don't understand why these fields are blank. 

 

3 REPLIES 3

rushikeshvartak
All-Star
All-Star

Instead of actual logic . Does hardcoded values works ?

please share logs


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

The issue isn't the data, it's how Saviynt is extracting that data in the task.

 

In version 23.9, the log is showing the ranked owners as follows: 
USEROWNERSADDED:[ALL:[U414577, U370989], 1:[U370989], 2:[U414577], 3:[], 4:[], 5:[]]
 
In version 24.1, the log is showing the ranked owners as follows:
USEROWNERSADDED:[ALL:[U400401], 1:[], 2:[], 3:[], 4:[], 5:[]]]
 
Given this information, it appears in 24.1 that the username is NOT being put into the correct rank as it was in 23.9. This looks to be a bug to us as the ranks are empty upon provisioning. I have already opened a Saviynt ticket for this issue, but have yet to receive a response.

looks like bug please raise support ticket


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.