and more in a single search tool across platforms. Read the announcement here. |
10/02/2023 06:02 AM
Version 5.5v
The OOTB DUO connector doesnt reconcile the account status properly. When an account is deleted in DUO , when the same is reconciled , Saviynt makes the status of the account as inactive and account name is suffixed with deleted. Ideally the status of the account here should be 'SUSPENDED FROM IMPORT SERVICE'
{
"userAccountsJSON": {
"accountID": "user_id~#~char",
"name": "username~#~char",
"displayName": "realname~#~char",
"customproperty4": "email~#~char",
"customproperty5": "last_login~#~datesec",
"customproperty6": "notes~#~char",
"customproperty7": "alias4~#~char",
"customproperty8": "alias1~#~char",
"customproperty9": "alias2~#~char",
"customproperty10": "alias3~#~char",
"customproperty13": "groups.name~#~char"
}
}
10/04/2023 07:54 AM
Hi @Vajra
Please check the variable inactivateaccountsnotinfile = false config in status threshold config , if its already there please check the logs to see what action is taken by accounts which are not coming as part of connector logs.
Thanks
Darshan
10/04/2023 08:02 AM
Hi Darshan,
The DUO OOTB connector doesnt support any statusthreshold config. So this cannot be accomadated. looks like its a bug in DUO connector. As if a user account is removed/deleted from DUO it should ideally make the account status to 'suspended from import service' in saviynt when the reconciliation happens. This was not happening so we thought to do it from custom query which again was not working due to foreign contraints issue due to the arstasks table integrity.
hope this clears the air.
thanks
thrinaath
10/04/2023 08:09 AM
Hi @Vajra
Okay yes the status threshold is missing for Duo connector and it is already taken as enhancement, and for status to be updated correctly it was accepted as a bug and fixed in v5.5 3.20 version
Thanks
Darshan
10/10/2023 09:42 AM
This is an unsolved problem
10/10/2023 12:26 PM
Hi @Vajra ,
Not sure what do u mean by unsolved problem? The below issue is fixed in v5.5 3.20 version , you need to get your env upgraded to 3.20 to get this working.
Thanks
Darshan