Questions about web service saas connectors vs VA connectors

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

I’m not sure if this is right place to ask the below questions:

Will Web Service SaaS connector be as flexible as VA based Web Service Connector? I mean, before rule and after rule allows us to write a custom code and change the requestEndPoint full URL, header, body , is this possible using Web Service SaaS connector?

2

I doubt it, there would be way more restrictions since it is all cloud based.

3

SaaS Connectors dont support connector rules based customisation. So you need to resort to below linked options to perform any sort of customisation. And currently those are only ones allowed.

1 Like
4

VA Connector:
Pros

  1. Customize the requests using Operation Rules if applicable
  2. VA logs to debug

Cons

  1. VA Dependency
  2. Additional Infrastructure

SaaS Connector:
Pros

  1. No need of VA, even if VA is down it will work.
  2. When SailPoint releases SaaS connectors for all the sources then you can have 100% cloud implementation.

Cons

  1. No Rules to customize, but customizers are introduced, need to see how extent it can replace operation rules)
  2. No logs, dependency on SailPoint ES for logs which is time consuming
  3. Not all the features are available compared to VA connector, so look at the supported features before choosing between VA and SaaS connector.

So if it is WebSerices connector, if you don’t need operation Rules then choose SaaS connector. If more customizations are required then go with VA connector.

For other connectors like SCIM, Salesforce, Atlassian…etc you can go with SaaS connectors if it has supported features which you need.

Thanks
Krish

5 Likes
5

I have a below 2 use-cases for webservice connector.

  1. Generate a JWT token using separate login endpoint, and JWT token is valid only for 30 minute. There is an security restriction on login endpoint to max allowed 10 API calls per minute.
  2. when login endpoint responds , payload contains the JWT token as well as server URL. Server URL is dynamic and it could be different on each login and we need to use the server url as base url for other endpoint with provided JWT. otherwise JWT won’t work.
    Now I’m looking for IDEA how can we achieve this using Web Service SaaS connection and its customizers ?
6

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