Connection Reset in active directory

Identity Security Cloud (ISC) ISC Discussion and Questions
1

Hi All,

Any idea on how we can fix the below error for active directory aggregation ?

[ERROR 1] java.lang.RuntimeException: sailpoint.connector.ConnectorException: [ ConnectorException ] [ Error details ] Connection reset

2

@Prashanth1812 Can you please increase the timeout and try?

Regards,
Shekhar Das

3

I did it throws me same error Shekhar

[
  {
    "op": "add",
    "path": "/connectorAttributes/healthCheckTimeout",
    "value": 180
  }
]
4

The default value is 180 seconds. If the timeout error continues, increase the value in 90 second increments and try again

5

@Prashanth1812 please increase aggregateTimeout

6

@Prashanth1812 ,
I suggest checking the Firewall rules where the VA and IQService servers are installed.
Traffic should be allowed between VAs IQServer and Active Directory server.

Thanks,
Vaibhav

7

Agree with @vdivakar can be either of these cases as well.

8

Test connection is working, but throws connection reset error in aggregation only.

10

Sure, will try it Thanks

How do I do this @shekhardas1825

11

If you are asking about increasing aggregation timeout then you have to increase in same way you updated it for healthCheckTimeout

Use partial source update API.

Regards,
Shekhar Das

1 Like
12

I have increased connectionTimeout: 270 and aggregatetimeout:180. Account aggregation gives me same error.

13

@Prashanth1812 In your connector configuration, can you validate that on the domain settings page that you have the correct domain DN? For example, if my path to my users is OU=Users,OU=Corporate,DC=MYDOMAIN,DC=COM, on the Domain Settings page, I would only put the DC=MYDOMAIN,DC=COM.

Then on the Account and Groups Settings page, you would enter the OU=Users,OU=Corporate,DC=MYDOMAIN,DC=COM in the search DN. If you have a search filter I would remove it until you get a successful search completed.

The second thing to try would be if you are attempting this aggregation with TLS configured, try using port 389 without TLS.

Alicia

14

I am facing the same error, even after increasing healthCheckTimeout as well as validating domain settings.

@shekhardas1825 were you able to resolve your issue?

16

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