Timeout Error When Connecting SailPointNow to Active Directory

Hi Experts,
I am encountering an issue while trying to establish a direct connection between SailPoint Now and Active Directory. Despite configuring all the necessary settings, I am consistently receiving a “Timeout waiting for response” error.

image

Could anyone provide insights into what might be causing this timeout error?
OR Are there any specific logs or settings I should review to resolve this issue?

Hi @rohitmisal45
could you please try to increase timeout and see if that works.
please check below link and see if it helps you to resolve problem: Timeout Errors and Settings

Could you please provide more details on where I can increase the timeout setting?

Hi @rohitmisal45 ,
You need to use the Partial Source Update (https://developer.sailpoint.com/idn/api/v3/update-source) API to modify the timeout value.

2 Likes

Hi @rohitmisal45

Check your VA is in connected state and the ccg version of VA is available in IDN.

If yes, check the ccg log in VA. Else, try restarting the VA. Also, try increasing the timeout settings as @gourab said.

Thanks!!

@GOKUL_ANANTH_M
I have check VA is in Connected state with CCG version.


Is this the correct way to increase timeout? If not, could you please suggest how to do it?

2 Likes

Then you can check the logs, even if the same error shows after increasing the timeout too.

After hit API the response is

Just verify that in endpoint headers, have you checked - Content-Type → application/json-patch+json

2 Likes

Hi @rohitmisal45 ,

  1. Do check your firewall settings to allow incoming requests.
  2. Check if you’re able to ping your AD from the VA.
  3. You can also keep the ccg.log file open to check if there is a request is going through to AD from VA.

Thanks.

3 Likes

Hello @poornasai

  1. I’m not sure where to look for firewall-related settings.
    2.Upon attempting to ping AD to VA, I received a connection by IP but a hostname
    failure (temporary failure in name resolution).
  2. The log file is open.
1 Like

Hi @rohitmisal45,

Use nc command from VA to check if there is communication between AD and VA on the specified port. This could determine if the port is blocked by a firewall.

Thanks.

Hi Everyone,

Thank you all for your responses and help! I’m happy to report that adding the IP address of the AD server resolved the issue.

1 Like

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