Web Services SaaS Connector - Base Config and Test Connection

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

Hi ISC community,

First time we’re trying to create a Web Services SaaS Connector & this is the first time I’ve tried to create one, so this is all new learning for me. Traditionally used OOTB connectors and the odd SQL connector but never before a Web Services SaaS.

We’re having some difficulties setting up the initial test connection and I suspect I’ve butchered the config… Trying to follow the documentation, I am already hitting a few hurdles trying to get basic config right:

  1. Noticing a few ISC-variables being used in the examples, such as: $application.client_secret$, $plan.native identity$… Is there a list or catalogue of ISC config variables?
  2. We get an error message when hitting Test Connection, where can I see the details behind this error as it doesn’t appear in the ISC events search.

Appreciate all the help we can get.

Cheers

2

Hello Sean,

You can review the java doc por ISC here Java docs | SailPoint Developer Community

And for the second question, you can check it through postman to know what is failing

Regards,

Pablo

1 Like
3

@SeanK-W can you share how you are connecting and authenticating if you are using API token then you can use the below sample

image
image1227×520 15.9 KB

image
image1231×444 13.4 KB

4

Hi @SeanK-W

Did you follow the steps in this documentation Connection Settings on how to setup the web services SaaS connector?

Also, what’s the error message are you getting and can you share a screenshot of it?

5

Hi all,

Firstly, thank you for the replies. We’ve been able to make some progress and test connection is working.

@pablonovoa this is exactly what I was after re the list, I’m surprised this isn’t referenced in the web connector documentation. Thank you! Bookmarking that one.

Re Postman, understood we could re-create the call within the tool; however unfortunately this won’t give us visibility on the error between our Web Services Connector > Web Service App…

Do you know of a way we can see this? For example, on account aggregation we’re hitting issues re Paging. Would be great to have visibility as to what exactly our connector is sending outbound.

@schattopadhy we are connecting via oAuth 2.0, we have the test connection up and running now so we no longer need help there. Thank you.

@nhassan Yes we are following the steps there, although the documentation is pretty light in terms of examples and useful references to assist with issues. EG the site Pablo linked above isn’t even referenced!

6

Paging can be dealt with in the connector config or using a rule. This documentation (and the sub-links on the page) will help:

Aggregation Paging

7

Thanks @vkashat ,

We’re having an issue where the target system has around ~10k accounts but the aggregation is only pulling in 1000.

We’ve tried to edit the paging and we’ve managed to get it reading 2000 - but have hit a wall.

This is what we’re trying so far, happy to take any advise from people as to where we’re going wrong:

$pageIndex$ = 0
 
$endpoint.fullUrl$ = $application.baseUrl$ + "/Api/v1/People/Search?External=false&ViewModelType=1&IsDeleted=false&SortField=lastname%2C%20firstname&SortOrder=asc&PageSize=1000&PageIndex=" + $pageIndex$
 
$pageIndex$ = $pageIndex$ + 1
8

Take a look at the different paging options:

image
image468×234 4.57 KB

There’s sample code on those pages that might help, for one you’ll need a way to terminate the aggregation once there are no more records.