Click HERE to see how Saviynt Intelligence is transforming the industry. |
07/29/2024 05:18 AM
Hi Team,
We have a LDAP based AD connector that removes group and account linking on all accounts when an account import job runs. It gets linked back when we run the access import job.
groupImportMapping :
{
"entitlementTypeName":"member",
"importGroupHierarchy":"false",
"performGroupAccountLinking":"true",
"accountNameMapping":"nameinnamespace=${accountsDn}",
"groupObjectClass":"(objectclass=groupOfNames)",
"mapping":"memberHash:member_char,entitlement_value:nameinnamespace_char,displayname:cn_char,customproperty2:nameinnamespace_char,customproperty4:description_char,RECONCILATION_FIELD:customproperty2"
}
STATUS_THRESHOLD_CONFIG
{
"statusAndThresholdConfig": {
"statusColumn": "customproperty10",
"activeStatus": [
"Active"
],
"inactiveStatus": [
"Inactive"
],
"deleteLinks": false,
"accountThresholdValue": 1000,
"correlateInactiveAccounts": true,
"inactivateAccountsNotInFile": true
}
}
Do you see if there is any config that we are missing or is this is the way it behaves ?
Regards,
Supriya
07/29/2024 08:36 AM
Could you kindly provide a detailed snapshot of the information extracted from the logs, encompassing errors and other pertinent functionality details encountered during the execution of this process? Your assistance in furnishing this information would greatly aid in the analysis and resolution of any issues .
‼️‼️⚠️Do not upload any attachments that contain sensitive information, such as IP Addresses, URLs, Company/Employee Names, Email Addresses, etc.⚠️‼️‼️
08/01/2024 04:10 PM
As discussed on the call
the ldif of account does not contain membership info , so this is the expected behaviour.