Click HERE to see how Saviynt Intelligence is transforming the industry. |
10/26/2023 09:55 AM
Hello everyone,
I am trying to reconcile groups from Oracle IDCS target using REST connector. During the reconciliation, we need to categorize entitlements based on the entitlement display name.
If entitlement name starts with "OBIEE_CORP_xxxx", map it to entitlement type "OBIEE_CORP".
If entitlement name starts with "OAC_CORP_xxxx", map it to entitlement type "OAC_CORP".
If entitlement name contains "OAC_CORP_xxxx_Admin", map it to entitlement type "OAC_CORP_Admin".
When i am running the full import, i am always getting first entitlement type [OBIEE_CORP] and it's associated entitlements but for other enttypes, just entitlement types are being listed under endpoints tab but none of the entitlements are being associated with respective ent type.
I suspect there is some issue with my json and pagination logic.
Attached is the "ImportAccountEntJSON" file which I am using.
Group search urls with search criteria are working fine in postman.
Could anyone help me to resolve this issue.
10/31/2023 09:15 AM
Can you check if the url defined for other entitlement types is working from Postman. if it is giving the output from postman, can you update ConfigJSON param in the REST connection with value {"showLogs":true}.
This will enable additional logging. In the logs check for the url and see if it getting any response data.
You can also refer to below REST Documentation for JSON examples and check for the required format (Section - Examples for JSON Construction and Developers Handbook)
https://docs.saviyntcloud.com/bundle/REST-v23x/page/Content/Examples-for-JSON-Construction.htm
11/01/2023 02:46 AM - edited 11/01/2023 02:48 AM
Thanks for the response Sahil.
I am getting the result in postman for all other entitlement types.
After enabling the logs, I could see that pagination url [nextUrlPath] is infinitely being executed for the first entitlement type and it is never ending. Always printing below lines and job is not getting completed.
Could you please help me out with this issue. below are the initial and nextURLPath I am using in my json.
Initial URL: https://url.identity.oraclecloud.com/admin/v1/Groups?filter=displayName+sw+%22OBIEE_CORP%22+and+not(...
nextUrlPath: ${response?.completeResponseMap?.itemsPerPage<50?null:'https://url.identity.oraclecloud.com/admin/v1/Groups?filter=displayName+sw+%22OBIEE_CORP%22+and+not(...'}
11/01/2023 07:47 AM
In case the next url path is being executed infinitely, the pagination logic in your JSON is causing the issue. You can refer the below REST documentation for different pagination examples provided and modify your JSON accordingly. Your pagination should have a logic to identify when is the last page of your api call and not search further.
https://docs.saviyntcloud.com/bundle/REST-v23x/page/Content/Developers-Handbook.htm
11/24/2023 06:37 AM
Thanks Sahil for your response. Sorry for the late reply.
After going through the documentation, I am able to reconcile all the groups with below pagination block in ImportAccountEntJSON. But the problem is, now it is not bringing the memberships into Saviynt from Oracle IDCS. Anything needs to be changed in my json?
"pagination": {
"offset": {
"offsetParam": "startIndex",
"batchParam": "itemsPerPage",
"batchSize": 50,
"totalCountPath": "completeResponseMap.totalResults"
}
}
Thanks,
Harish
11/24/2023 10:28 AM
Is the membership information not imported for all the Entitlement types or any specific one.
11/26/2023 08:04 PM
It is not importing for all the entitlement types.