12/06/2022 03:47 AM
Hi,
We need to disable Exchange account for a user on termination. However, that is triggered via powershell script for license disablement on exchange.
We are able to pass the http params via update account json, which includes the username of the user alongwith the location of the powershell script, which works and disables user's license on Exchange on termination, but the user still shows as manually provisioned in Saviynt.
However, can the same parameters be passed via Disable Account Json, so that the user is disabled in EIC as well, which currently shows manually provisioned.
Attaching my update account code:
{
"call": [
{
"name": "call1",
"connection": "acctAuth",
"url": "<url>",
"httpMethod": "POST",
"httpParams": "{\"Script\":\"Powershell.exe -File c:\/Scripts\/ExchangeDisable.ps1 \\\"${user.customproperty17}\\\"\"}",
"httpHeaders": {
"Authorization": "${access_token}"
},
"httpContentType": "application/json",
"successResponses": [
{
"message": "ProfileID Created Successfully"
},
{
"message": "ProfileID Updated Successfully"
}
],
"unsuccessResponses": {
"statusCode": [
400,
401,
404,
405,
500
]
}
}
]
}
12/06/2022 07:51 PM
You can pass. Are you facing any issue ?
12/06/2022 08:30 PM
Hi Rushi,
We are getting a Null Pointer Exception on passing the Script path and attributes in http params in disable Account JSON
12/06/2022 08:48 PM
Sha
The bindings supported are:
|
12/07/2022 04:20 AM
Hi,
The disable account JSON throws Null Pointer Exception. Any modifications in this that you can suggest?
This script passes the script path along with the user attribute that is used to disable the user's license
{
"actions": {
"Disable User": {
"call": [
{
"name": "call1",
"connection": "acctAuth",
"showResponse": true,
"url": "<url>/${account.accountID}",
"httpMethod": "PUT",
"httpParams": "{\"Script\":\"Powershell.exe -File c:\/Scripts\/ExchangeDisable.ps1 \\\"${user.username}\\\"\"}",
"httpHeaders": {
"Authorization": "${access_token}"
},
"httpContentType": "application/json",
"successResponses": [
{
"message": "success"
}
]
}
]
}
}
}
12/07/2022 01:43 PM
task.username
12/08/2022 07:13 AM
Still getting the error with task.username.
12/08/2022 07:23 AM
task.userKey.username
12/08/2022 08:21 AM
This too isn't working.
Since via Update account task the user license can be disabled, can we run disable account task in Saviynt wherein the user gets suspended on Saviynt endpoint?
The update account task would anyway disable the users license on termination.
But the user should not reflect as manually provisioned in Saviynt
12/08/2022 11:51 AM
You can't change status on updateaccount task
12/08/2022 09:10 PM
That is right. Hence asking for Disable account JSON.