Web service Connector

Hello,

To identify if a system is fit to be connected to SailPoint using a web service connector, is there a template/check list that we can use? What are the things to consider to see if an application is fit to be connected through web services connector.

Thanks,

Lakshmi.

Please consider addressing the following when creating your topic:

  • What have you tried?
  • What errors did you face (share screenshots)?
  • Share the details of your efforts (code / search query, workflow json etc.)?
  • What is the result you are getting and what were you expecting?

Hi @Laks

To check if a system can be connected to SailPoint via a Web Service connector, you can use a simple checklist:

  1. API Availability – Does the system have REST or SOAP APIs with proper documentation?

  2. Authentication – Can it support OAuth, API keys, or basic auth, and does the user have proper permissions?

  3. Data Access – Can all required user attributes be retrieved? Is there a unique identifier for each account?

  4. Provisioning – If needed, can accounts be created, updated, or deleted through the API?

  5. Connectivity & Performance – Is the API accessible from SailPoint? Any rate limits or timeouts to consider?

  6. Testability – Is there a sandbox environment to test before production?

A simple Yes/No table with notes for each of these points usually helps decide if a system is fit for connection.

2 Likes

@Gopi2000 Thank you.

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