Webservices SaaS Connector – Customizer for Account Aggregation

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

Hi,

I am currently working on a Webservices SaaS connector, where the account aggregation process involves multiple steps:

  1. Retrieving all accounts.
  2. Fetching additional user details (more attributes) for each user.
  3. Retrieving group memberships and other entitlements by calling different API endpoints.

I have a few questions regarding the implementation:

  1. Achievability via Customizer:
  • Can this be implemented using a Customizer in a manner similar to an AfterOperationRule?
  1. Passing User ID to Subsequent Customizer Function:
  • If so, how can I pass the user ID from the initial response to the subsequent Customizer function (presumably afterStdAccountList)?
  1. Binding API Responses to User Accounts:
  • How can I consolidate all API responses and map them to user accounts before returning the account object?

I appreciate any guidance or best practices on this approach.

Best regards,
Pooja

2

Hi @poojapal0204

If my understanding is correct Retrieve all accounts endpoint is fetching the userID of the user, this can be passed to the subsequent operation as $response.userID$ to fetch the additional attributes from other 2 endpoints.

Refer to Parent Endpoint section in this doc for more details on configuring multiple endpoints for aggregation

Hope this helps

Thank you

1 Like
3

Also, add all the required attributes in the Account schema and Entitlement schema, and map them respectively in each aggregation operation.

Thank you

1 Like
4

Hello @rkhade Here I am talking about Customizers because the endpoints are not straight forward to get the other entitlement details hence I can’t user the child operations in aggregation and AfterOp rule seems doesn’t apply on WS SaaS connector hence relying on customizers to get some help on this.