Using SaaS connector vs Creating webservice sources for loopback connector

Hello,

I want to configure IdentityNow loopback connector by configure a webservice connectors.

But i see in collab a SaaS connetor for IdentityNow loopback :

What is the difference beetween this two connectors and pro/cons ?

1 Like

The main difference is that the SaaS connector will not have to go through your on-prem VA’s to contact the SailPoint APIs.

Another benefit of the SaaS connector is that you have better control on what happens within the connector and can customize (via customizers) or even modify the connector if you want to alter its behavior.

1 Like

I prefer to use Webservices as i can customize and update it faster.
yeah it uses the VA but :man_shrugging:

Best!

1 Like

I differ on better control part here. They have removed VA which is good part but with VA gone it has become black box. If you have any issues in Saas based connectors you are totally dependent on support/services for troubleshooting. There are no logs anywhere until and unless you have developed it yourself. I am only referring to those developed and release by sailpoint connector team itself which is not the case here but just wanted to share my feedback on that specific “better control” part

2 Likes

The Loopback connector linked here is open source and you can edit it to your hearts content.
For SaaS connectors you can get the logs yourself via CLI tool, or you can tail them.

It works just fine, give it a shot!

1 Like

Plus, if you create your own SaaS connector, or slightly modify the code of the above mentioned connector, you can pretty easily log whatever you want / need for your debugging purposes! This is way easier to obtain and read than the VA based logs.

1 Like

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.