WebService Connector Failure — Error 500 with java.lang.reflect.InvocationTargetException

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

Hello SailPoint Support Team,

We are experiencing a critical failure with one of our WebService connectors. This connector had been working normally for a long time, but suddenly stopped functioning without any recent configuration changes on our side.

The console now returns the following error for any operation:

Message Status(500) Error response from connector: java.lang.reflect.InvocationTargetException

Even after removing sensitive parameters such as Client ID, Client Secret, and BaseURL, the connector continues to fail with the same error.

Troubleshooting Performed

To ensure this was not a connectivity issue between our Virtual Appliance (VA) and the target endpoint, we performed several tests:

:check_mark: Port test using nc

nc -zv -w 10 api.eu.adp.com 443

Result: Connection successful

:check_mark: HTTPS connection test using curl -v

curl -v https://api.eu.adp.com

Result: TLS handshake and connection successful

These confirm that the VA can successfully reach the external endpoint.

Behavior Inside ISC

Despite the successful connectivity tests, any operation in the WebService connector fails immediately with the same internal error:

java.lang.reflect.InvocationTargetException

This happens even when:

  • Credentials are removed

  • BaseURL is removed

  • We perform operations that should not call the remote endpoint

This suggests the issue is likely internal to the connector, not coming from the target system.

Help me

2

is it working in postman? have you checked

3

Yes, it works through the postman.

4

Could you increase the connector’s healthCheckTimeout and also increase other timeout if required and test it again?

Also check the log statement in ccg.log file and see whether you are able to get more details about this error and it may help you to know the root cause.

Since you said it is giving you the same error even without credentials, could you double check the connector configuration again like URLs, endpoints.

5

Have you opened a ticket with support?

6 
I'll open it today for the Sailpoint team.
7 
Could you increase the connector's healthCheckTimeout and other timeouts if necessary, and test again?

A: I will increase it and test.

Also check the log in the ccg.log file to see if you can get more details about the error. This may help identify the root cause.

I will look into it with our client.

Since you know the same error occurs even without credentials, could you double-check the connector configuration, such as URLs and endpoints?

I checked and it's correct, even after adjusting or removing it, it continues the same.
1 Like
8

I’ll open it today for the Sailpoint team.

1 Like