Strange API behavior v3/identity-profiles

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

Hi everyone,

If we run the GET API /v3/identity-profiles, we notice some inconsistent behavior.
See two different mappings in the same identity profile below. They both link to a transform.
The first one is elegant in that it does not show redundant information. The second one does show some information twice, namely the type=reference part and it mentions the name of the transform twice (they say it is the id, but actually it is the name of the transform).

Is this done on purpose? In which cases does it contain redundant information and in which cases does it show the elegant way?

[{
    "identityAttributeName": "example1",
    "transformDefinition": {
        "type": "reference",
        "attributes": {
            "input": {
                "attributes": {
                    "attributeName": "attribute a",
                    "sourceName": "my sourcename",
                    "sourceId": "2c91808780d932123480e0f1d1234ba4"
                },
                "type": "accountAttribute"
            },
            "id": "IdenAttr - set example1"
        }
    }
},
{
    "identityAttributeName": "example2",
    "transformDefinition": {
        "type": "reference",
        "attributes": {
            "input": {
                "attributes": {
                    "attributeName": "attribute a",
                    "id": "IdenAttr - set example2",
                    "sourceName": "my sourcename",
                    "type": "reference",
                    "sourceId": "2c91808780d932123480e0f1d1234ba4"
                },
                "type": "accountAttribute"
            },
            "id": "IdenAttr - set example2"
        }
    }
}]
1 Like
2

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