Identity Attribute with Account Attribute value

Identity Security Cloud (ISC) ISC Discussion and Questions
,
1

Hello Team,
I need one help, As per requirments, one Identity Attribute under identity profile is mapped with another account’s one attribute, all works fine, but when that another account is deleted then that identity attribute is wiped out too, which should be. But in my case of if accounts got deleted, I dont want to wipe out my identity attribute and I want to preserve it. Any guess How I can do it?

2

@singlde , Identity attribute itself cannot be removed if value doesn’t exist for the mapped account attribute. If needed, you can mark/populate the identity attribute value as null.

3

not sure, as soon as mapped account attribute is deleted, mapped Identity attribute gets deleted too.

4

You mean that Identity attribute is deleted ?

or value in that Identity attribute is wiped out.

5

Hello Krishna, value in that Identity attribute is wiped out.

6

Build Transform like this, if there is not value from account attribute then it will get the current value of Identity attribute.

{
    "type": "firstValid",
    "attributes": {
        "values": [
            {
                "type": "accountAttribute",
                "attributes": {
                    "sourceName": "source1",
                    "attributeName": "att1"
                }
            },
            {
                "type": "identityAttribute",
                "attributes": {
                    "name": "IdentityAttName"
                }
            }
        ],
        "ignoreErrors": false
    }

}
7

Hi @singlde ,

To prevent identity attribute values from being wiped out when a mapped account is deleted, you can modify your transforms by using the “requiresPeriodicRefresh” attribute. This attribute is an optional configuration for transforms that, when set to true, indicates the transform logic should be reevaluated every evening as part of the identity refresh process.

By setting “requiresPeriodicRefresh” to true, you ensure that the transform will be recalculated regularly, even if the source account has been deleted. This helps maintain the identity attribute values independently of the account’s status. Additionally, you can use more complex transform structures to ensure data persistence. For example, you could implement a “firstValid” transform that checks multiple sources for the attribute value. This way, if one account is deleted, the transform can fall back to other valid sources to maintain the identity attribute value.

Here’s a basic structure of how you might set up such a transform:

  1. Use a “firstValid” transform as the main transform.
  2. Within the “firstValid” transform, include multiple “accountAttribute” transforms, each pointing to a different source.
  3. Set “requiresPeriodicRefresh” to true for the main transform.

This approach allows the system to check multiple sources for the attribute value, reducing the risk of data loss when a single account is deleted.

8

Thanks Krishna, it seems to be working, I tried same thing but one difference was

"type": "identityAttribute",
                "attributes": {
**"sourceName": "XXXX",**
                    "name": "IdentityAttName"
                }
9

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.