Issue with Multiple Account Aggregation end points

[Divya_Kusumula03 (Divya Kusumula)]

We have two account aggregation points in place:

Aggregation-1: This provides an email ID and a set of groups (after an operation rule is applied to modify the groups as required).
Aggregation-2: This uses the email ID to retrieve a different set of groups.

The following configurations have been implemented:

Created two account aggregation HTTP operations: aggregation-1 and aggregation-2.
Marked aggregation-1 as the parent operation for aggregation-2.
Updated the endpoint configuration as " /user/name/$response.Email$/groups/get " Email is a schema attribute, which is sourced from the after operation rule applied to aggregation-1.

Encountered below error
sailpoint.connector.ConnectorException: Url: https://abc.com/rest/v1/permission/user/name//groups/get, Message: 404 : Not Found : {“success”:false,“msg”:“HTTP 404 Not Found.”,“id”:-1}, HTTP Error Code: 404
Please suggest if any configuration need to be changed

Thanks,
Divya

[KRM7 (Krishna Mummadi)]

@Divya_Kusumula03

Encountered below error
sailpoint.connector.ConnectorException: Url: https://abc.com/rest/v1/permission/user/name//groups/get

there is double slash in URL. That is why 404 error.

[Divya_Kusumula03 (Divya Kusumula)]

below images shows the configured end point

But in the error message it is showing as two slashes //
/permission/user/name//groups/get

[officialamitguptaa (Amit Gupta)]

@Divya_Kusumula03 -

The error you’re encountering indicates that the Email value is not being correctly substituted in the URL of your second aggregation operation (aggregation-2). Specifically, the URL shows a double slash (//), suggesting that the Email variable is empty or not being accessed correctly:

Url: https://abc.com/rest/v1/permission/user/name//groups/get

Understanding the Issue

• Empty Variable: The segment user/name//groups/get has an empty value between name and groups, meaning $response.Email$ is not providing a value.
• Variable Scope: In the context of chained HTTP operations, accessing variables from a parent operation requires specific syntax.

Solution

Check if you have updated the response Mapping for aggregation-1 (Below is mine)

Also make sure you have updated the parent Endpoint to aggregation-1 for aggregation-2 HTTP Operation -