Webservice after rule

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

Hi Team,

Has anyone tried this usecase?

my endpoint returns all accounts, I thinking to loop them in after rule to check if user attribute sysID = 100, only return the accounts.

I only want to only aggregate the users whose sysId = 100.

2

Hi Chandra,

I’d check first with the API doc / endpoint team to be sure that there isn’t an ability to filter on your list account endpoint. It’s better to filter on the API than to create an after rule to handle it.

Thanks,
Margo

3

@margocbain

Yes, API doesnot support filter on this attribute.

4

Check this post, maybe it will help :
Web Service connector After Operation Rule account filtering - Identity Security Cloud (ISC) / ISC Discussion and Questions - SailPoint Developer Community

5

Hello @chandramohan27,

IdentityNow Account Filtering during Account Aggregation - Compass

I think this will help you without the need of a rule!

6

Hi Chandra,

“script”: “import java.util.List;\nimport java.util.ArrayList;\nimport java.util.Map;\n\npublic class FilterAccountsBySysID {\n\n public List afterAggregation(Application application, List accounts, Object connector, Object context) {\n List filteredAccounts = new ArrayList<>();\n\n for (Map account : accounts) {\n Object userObj = account.get("user");\n if (userObj instanceof Map) {\n Map user = (Map) userObj;\n Object sysID = user.get("sysID");\n if (sysID != null && sysID.equals(100)) {\n filteredAccounts.add(account);\n }\n }\n }\n\n return filteredAccounts;\n }\n}”
},

call this rule after your HTTP Operation

7

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