Issues with Correlation Not Working for Any matchMode in ISC Beta API

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

Hello team,
I’m having trouble getting account correlation to work with any matchMode using the update correlation API. No matter which match mode I choose (e.g., ANYWHERE, START, END.), the correlation doesn’t seem to work as expected. Has anyone tried using this API before with match mode?
Here’s the JSON body I’m using for the API:

> {
>     "attributeAssignments": [
>         {
>             "complex": false,
>             "property": "email",
>             "operation": "EQ",
>             "value": "e-mail",
>             "ignoreCase": false,
>             "matchMode": "START",
>             "filterString": null,
>            
>         }
>     ],
>     "id": "**************",
>     "name": "*************"
> }
3 Likes
2

When you say its doesn’t work as expected, can you provide more detail?

3

Hi @anagha ,

As you gave the “matchMode” as START, I believe you should give some values in “filterString” which says what to filter out in email and then match it with identity attribute

4

It just doesn’t correlate

5

I tried updating the ‘filterString’, but it’s not working. It still shows up as “null”.

1 Like
6

Is there any necessary requirement to have “matchMode” for email attribute? If not, can you keep it as null and try to correlate?

7

I have just tried this with email and it worked for me


    "attributeAssignments": [
        {
            "complex": false,
            "property": "email",
            "operation": "EQ",
            "value": "UniqueIdentifier",
            "ignoreCase": true,
            "matchMode": "ANYWHERE",
            "filterString": null,
            "sequence": 1
        }
    ],
    "id": "xxxx",
    "name": "xx [source] Account Correlation"
}
8

Did you give the same values for ‘email’ and ‘uniqueIdentifier’ ? I want to know if ANYWHERE allows for partial matches within the string

1 Like
9

They were the same value, let me check

10

For me, ANYWHERE did not allow partial matches.

I have also tried adding a filter but the filter does not save, I suspect the ANYWHERE match requires a filter to be defined.

3 Likes
11

I’m facing the same issue as well. Is this a known issue ?

12

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