Correlation Rule issues

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

Hello everyone. I’m facing issues with my correlation rule for accounts. In my rule, I’m using this snippet:

List identities = idn.findIdentitiesBySearchableIdentityAttribute(“documento”, EQUALS_FILTER, documento, “documento”);

to list identities based on the mentioned attribute. I’m also using this for import:

import sailpoint.server.IdnRuleUtil;

However, I’ve tried it this way and also just with “Equals” and I’m still facing issues with the rule.

Do you know how I can use this utility correctly?

2

Is this set as Searchable attribute?

1 Like
3

Hello,

Yes, this is set as a searchable attribute, identityattribute.

4

Hi @carolinebraga,

Your rule is not giving you correct output, or it is throwing some error?

Thanks

5

Hi @ashutosh08,

Does not trigger errors, it just doesn’t behave as expected, incorrect output. Does not correlate.

Thank you.

6

Hi,

I refer to this post - IdentityNow Correlation Rule - Identity Security Cloud (ISC) / ISC Discussion and Questions - SailPoint Developer Community

As per this, can you try to type cast the returned List to sailpoint.rule.identity type of list and see if it works.

List<sailpoint.rule.Identity> identities = idn.findIdentitiesBySearchableIdentityAttribute(“documento”, EQUALS_FILTER, documento, “documento”);

1 Like
7

Hi, thank you! I will try it this way.

I am using these imports:

import sailpoint.rule.Identity;
import sailpoint.server.IdnRuleUtil;
import java.util.HashMap;
import java.util.Map;
import java.util.List;

do you think any of them might be interfering?

Thanks.

8

Hi @carolinebraga,

Is it resolved?

If not, then can you add some logger statement and see till which line or execution statement you are able to go and after which logical step your code is returning incorrect response.

Thanks

1 Like
9

Yes, possibly.

Have you tried typecasting explicitly as I mentioned previously?

10

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