and more in a single search tool across platforms. Read the announcement here. |
03/15/2024 06:47 AM
We are using STATUS_THRESHOLD_CONFIG where we are trying to mark account as locked or unlocked based on lockouttime. If lockouttime value is 0 then unlock or for any other value locked. But it not working. We have tried only by passing only unlock value but that did not worked either.
STATUS_THRESHOLD_CONFIG:
{
"statusAndThresholdConfig": {
"statusColumn": "customproperty29",
"activeStatus": [
"512",
"544",
"66048"
],
"inactiveStatus": [
"546",
"514",
"66050"
],
"deleteLinks": false,
"accountThresholdValue": 15000,
"correlateInactiveAccounts": true,
"inactivateAccountsNotInFile": false,
"lockedStatusColumn": "customproperty31",
"lockedStatusMapping": {
"Unlocked": [
"0"
]
}
}
}
Value of lockouttime is not consistent in case of locked state but will be 0 in case of unlocked state. When we hardcode the value, something like this "Locked": ["132959598087830995"], then it works for the account that have lockouttime with this value. We have to somehow apply the logic for locked state that status should be locked when anything other than 0 is passed in lockouttime including null value.
We are importing lockouttime as string and also tried with millisec. CUSTOMPROPERTY31::lockoutTime#String
Any suggestions?
03/17/2024 06:34 PM
instead of STATUS_THRESHOLD_CONFIG for lock status use import json using CONST
03/18/2024 05:08 AM
I have tried this:
"customproperty31":: "#CONST#${(lockoutTime == '' || lockoutTime == null || lockoutTime = '0' ) ? '' : '1')}#String"
Error Log:
03/18/2024 06:33 AM
"customproperty10": "#CONST#${(1==1)?'true':'false'}~#~char",
try above simple and lockoutTime should be response.lockoutTime
03/18/2024 07:12 AM
Same error:
03/18/2024 09:28 PM
AD Connector may not support CONST
03/21/2024 10:15 AM
Hi @Tezinder
As mentioned in the document, lockedStatusColumn needs to be defined stating possible values for both Locked and Unlocked. Below is the syntax:
{
"statusAndThresholdConfig": {
"accountThresholdValue": 1000,
"statusColumn": "customproperty10",
"activeStatus": ["true"],
"deleteLinks": true,
"lockedStatusColumn": "customproperty22",
"lockedStatusMapping": {
"Locked": ["1"],
"Unlocked": ["0"]
}
}
}
Meanwhile as we check the solution to modify the import value and make it consistent to define in locked block, please confirm if the values for locked state consistent and do we have a defined list which can be used under locked state.
Referance:
https://docs.saviyntcloud.com/bundle/Alibaba-v24x/page/Content/Creating-a-Connection.htm
03/21/2024 08:51 PM
I have tried having locked and unlocked status both in the statusthresholdconfig.
The issues is lockouttime is not consistent. Connector is expecting it to be in 0 or 1 format but it is not. Locouttime status is "0" only in case when unlock action is performed on AD
There is no "1" there, rather it has timestamp of when the account is locked on AD which would never be consistent. That's problem and accounts are not getting locked on saviynt.
03/27/2024 09:17 PM
You can use #CONST
03/27/2024 12:04 AM - edited 03/27/2024 12:05 AM
Instead can you use useraccountcontrol and store it on a poperty in saviynt and include the expected status values under status threshold
Ex:
"lockedStatusColumn":"customproperty5",
"lockedStatusMapping":{
"Locked":[
"0"
],
"Unlocked":[
"1"
You can check the possible userAccountControl values here: