Updating values of Identity Attributes

Hi Everyone,

Is there any way to update the values of identity attributes apart from changing on the source level.

My requirement is: I am testing the account synchronization. I need to change the attribute value and see if the synchronization is reflecting in the target.

Thanks,

Sarvan Marri

@sarvanmarri While it’s possible to enable edit mode in IIQ by setting the editMode flag to true via the debug page, this functionality is not available in ISC.

To reflect changes in ISC, you must update the mapped value at the source level and then perform an aggregation into ISC to apply the update.

I’ve encountered this scenario myself while testing attribute synchronization. I had to modify the HR source attributes for a single account and aggregate it to verify whether the sync to downstream systems was functioning correctly.

1 Like

Hi @sarvanmarri

If this is only for testing purposes, I recommend replicating the source using a delimited file and performing the test there.

We cannot manually modify the Identity Attribute — changes can only be made through the source or transforms.
Please note that any updates made via a transform will impact all identities.

Thank you
Sid

1 Like

A potential workaround would be to create a delimited file source and add an account that will correlate to the identity from the authoritative source. Then in your identity profile mapping, have a transform that takes the firstValid of either the delimited file source, or the HR source.

So if HR source has schema: unique_id, first_name, last_name, email
Then delimited file source should have schema: unique_id, first_name, last_name, email
And transform for any attribute could be:

{
    "name": "whateverAttribute",
    "type": "firstValid",
    "attributes": {
        "values": [
            {
                "type": "accountAttribute",
                "attributes": {
                    "sourceName": "delimitedFileSource",
                    "attributeName": "attributeName"
                }
            },
            {
                "type": "accountAttribute",
                "attributes": {
                    "sourceName": "HR Source",
                    "attributeName": "attributeName"
                }
            }
        ]
    }
}

Using this approach will allow you to override the HR source attributes. A launcher with a form could provide a way to add delimited file source accounts in the UI.

Matt

1 Like

Gents,

Thank you for your response.

I found a way to update the required identity using the hardcoded transform as below. If it is my desired user, the attribute value will be updated. If not, it will just return the direct mapping without updates/changes.

{
  "attributes": {
    "expression": "$uid eq 1234",
    "positiveCondition": "$updatedValue",
    "negativeCondition": "$sameValue",
    "uid": {
      "attributes": {
        "name": "<Unique ID>"
      },
      "type": "identityAttribute"
    },
    "updatedValue": {
      "attributes": {
        "value": "<Updated Value here>"
      },
      "type": "static"
    },
    "sameValue": {
      "attributes": {
        "name": "<Attribute Name>"
      },
      "type": "identityAttribute"
    }
  },
  "type": "conditional",
  "name": "<Transform Name>"
}

Thanks,
Sarvan Marri

1 Like

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