Segregation of Duty search breaks on invalid input

Feedback Bugs
,
1

Hi team!

We try to define a SOD policy in IdentityNow.
We go to ui/search/policies/create/conflicting-access, then name our two access lists (A and B) and hit next.
We are now asked to search for entitlements. One of our entitlements has the following format:
my:chosen:entitlement. We search for it and get stuck in a neverending loop.

image
image1835×537 37.6 KB

We notice the following error in the developer tools:

{
    "detailCode": "400.1 Bad request content",
    "trackingId": "30750e896aea489a81951b8d69913909",
    "messages": [
        {
            "locale": "en-US",
            "localeOrigin": "REQUEST",
            "text": "Your search query was invalid, reason: {\"root_cause\":{\"reason\":\"parse_exception: Encountered \\\" \\\":\\\" \\\": \\\"\\\" at line 1, column 9.\\nWas expecting one of:\\n    \\u003cEOF\\u003e \\n    \\u003cAND\\u003e ...\\n    \\u003cOR\\u003e ...\\n    \\u003cNOT\\u003e ...\\n    \\\"+\\\" ...\\n    \\\"-\\\" ...\\n    \\u003cBAREOPER\\u003e ...\\n    \\\"(\\\" ...\\n    \\\"*\\\" ...\\n    \\\"^\\\" ...\\n    \\u003cQUOTED\\u003e ...\\n    \\u003cTERM\\u003e ...\\n    \\u003cFUZZY_SLOP\\u003e ...\\n    \\u003cPREFIXTERM\\u003e ...\\n    \\u003cWILDTERM\\u003e ...\\n    \\u003cREGEXPTERM\\u003e ...\\n    \\\"[\\\" ...\\n    \\\"{\\\" ...\\n    \\u003cNUMBER\\u003e ...\\n    \"}}."
        },
        {
            "locale": "en-US",
            "localeOrigin": "DEFAULT",
            "text": "Your search query was invalid, reason: {\"root_cause\":{\"reason\":\"parse_exception: Encountered \\\" \\\":\\\" \\\": \\\"\\\" at line 1, column 9.\\nWas expecting one of:\\n    \\u003cEOF\\u003e \\n    \\u003cAND\\u003e ...\\n    \\u003cOR\\u003e ...\\n    \\u003cNOT\\u003e ...\\n    \\\"+\\\" ...\\n    \\\"-\\\" ...\\n    \\u003cBAREOPER\\u003e ...\\n    \\\"(\\\" ...\\n    \\\"*\\\" ...\\n    \\\"^\\\" ...\\n    \\u003cQUOTED\\u003e ...\\n    \\u003cTERM\\u003e ...\\n    \\u003cFUZZY_SLOP\\u003e ...\\n    \\u003cPREFIXTERM\\u003e ...\\n    \\u003cWILDTERM\\u003e ...\\n    \\u003cREGEXPTERM\\u003e ...\\n    \\\"[\\\" ...\\n    \\\"{\\\" ...\\n    \\u003cNUMBER\\u003e ...\\n    \"}}."
        }
    ],
    "causes": []
}

It probably doesn’t like the colons here. But at least we should get an error message on screen instead of wondering why it takes so long for the SailPoint servers to find the results.
Searching for "my:chosen:entitlement" does work correctly.

Also using the standard search (while not creating an sod) does provide an error on the screen:

image
image991×278 12.2 KB

Kind regards,
Angelo