Share all details related to your problem, including any error messages you may have received.
Hi Everyone,
We wanted to integrate SAP concur with Sailpoint IIQ with OOTB connector but sailpoint does current connector does not support writeback of custom attributes. Similarly we are trying to use SCIM connector but we are unable to read accounts with mutiple endpoints for user information and decided to go with webservices connector.
Problem Statement:
The SAP Concur SCIM API’s have pagenation with “nextCursor” attribute in response and this needs to be passed in every API cvall for aggregation for pagenation of the user records.
We would like to know if someone already integrated concur as a webservice app or any other connector and need some inputs or suggestions.
We have integrated with concur , We did created all the required custom SCIM end points based on our requirement and then used OOTB SCIM connector to manager user lifecycle .
Hi Gautham, I will tell you my experience here, however, I know that it’s not the best practice .
Actually, we did the integration with a normal WebSerivce Connector and we did some after operation rules to achieve that…
So I can say that using a middleware is a better approach but it went like this because that was a customer need and can’t go with any middleware.
I think the Ver was 4.0
Most welcome @gbagari anytime!
as far as I remember it was with Offset pagination
total records, pageSize, and offSet… can’t remember the names exactly now, but that is what I remember at the top of my head, maybe when I look for the rule for you in my repos I will remember and give more insights .
I will check for the rules for you and definitely will share if I find any