Hello All,
UseCase: We are working on a usecase where we would like to generate ChangePassword Tasks from Saviynt for a new user
to Sync all passwords across respective endpoints associated with that user.
The intent is to create one ChangePassword task using User Update Rule for Sav4Sav Connection
and then based on that Passwordpolicy generate changepassword tasks for the other endpoints.
We have updated the ChangePasswordJSON and PasswordPolicyJSON of a SAV4SAV Connection with the following JSON:
ChangePasswordJSON:
-----------------------
{
"call": [
{
"name": "call1",
"connection": "userAuth",
"url": "ABCOrg.com/ECM/api/v5/changePassword",
"httpMethod": "PUT",
"httpParams":{
"username":"${user.username}",
"password":"${password} ",
"changePasswordAssociatedAccounts":"true",
"endpoint":"Endpoint1,Endpoint2,Endpoint3,Endpoint4",
"validateagainstpolicy":"Y" ,
"updateUserPassword":"true",
"setarstasksource":"true"
},
"httpHeaders": {
"Authorization": "${access_token}"
},
"httpContentType": "application/x-www-form-urlencoded",
"successResponses": {
"statusCode": [
201,
200,
204
]
}
}
]
}
PasswordPolicyJSON:
-----------------------
{
"minLength": 8,
"maxLength": 20,
"noOfCAPSAlpha": 3,
"noOfDigits": 2,
"noOfSplChars": 3
}
Test Results and Findings
------------------------------
-> Task was created only for Endpoint which we have specified in UserUpdateRule.
-> We are able to use ChangePassword API to createTasks for other endpoints but it's not functioning the same way in Sav4Sav(REST) connection.
->The mechanism to trigger ChangePassword Tasks only creates 1 task for the endpoint mentioned
in the rule.
When we try to provisioning that task to see if that would generate other tasks later it gives the error below.
{"auditDetails":{"call1":[{"message":"No signature of method: com.saviynt.provisoning.rest.RestUtilService.getDynamicBindString()
is applicable for argument types: (java.util.LinkedHashMap, java.util.HashMap) values: [[username:${user.username},
password:${password} , ...], ...]\nPossible solutions: getDynamicBindString(java.lang.String, java.util.Map)","status":"Failed"},
{"message":"No signature of method: com.saviynt.provisoning.rest.RestUtilService.getDynamicBindString() is applicable for argument types:
(java.util.LinkedHashMap, java.util.HashMap) values: [[username:${user.username}, password:${password} , ...], ...]\n
Possible solutions: getDynamicBindString(java.lang.String, java.util.Map)","status":"Failed"}]},
"call1":{"message":"No signature of method: com.saviynt.provisoning.rest.RestUtilService.getDynamicBindString() is applicable for argument types: (java.util.LinkedHashMap, java.util.HashMap)
values: [[username:${user.username},
password:${password} , ...], ...]\nPossible solutions: getDynamicBindString(java.lang.String, java.util.Map)","status":"Failed"}}
-> We have ensured that Security System has No Password Policy but there was a Password Policy created with same name of the application.
In our previous testing we noticed the following lines in the logs. Attached here.
Please do let us know if any one has faced a similar scenario and any suggestions on any other approach that can be followed.
