The healthy of Sailpoint Connector is "Disconnected" after configuration

Forum|Forum|1 year ago
April 8, 2025
1 reply
819 views

Hi There

Does anyone have the same experience as I do? Is the health of the Sailpoint Connector still not "available" after correct configuration?

Here are my settings

1. URL : HTTP://X.X.X.X/identityiq/scim/v2/

(The SailPoint server is located in the same subnet as FortiSOAR)

2. Input spadmin account and its password

3. Disable SSL verification

Got the error message as attached screen capture

I know that the KB said the connector version 1.0.0 had a bug and was fixed in 1.0.1. However, I still got the error.

However, I used the URL directly in the browser and got a "NOT FOUND" message returned by the SailPoint API

So, what is the correct URL I should input in the configuration?

Snipaste_2025-04-08_16-17-18.png

roshan_bangera

Explorer

Hello @simonyz_yeh,

It seems,

1) Network is working: You're not getting a timeout or connection error.

2) You're using connector version 1.0.1, which is the fixed version.

3) Endpoint is incorrect: The connector is trying to call a SailPoint API path that doesn't exist (404).

Can you help me with the connector logs please? This might give us more insight on what's going wrong! You can check for the connector logs here /var/log/cyops/cyops-integrations/connectors.log

Sign up

Login with SSO

Login to the community

Login with SSO