WebService Connection Failure with failed to respond, HTTP Error Code: 0

SailPoint Human Fabric (SHF) SHF Discussion and Questions
,
1

Hi Folks,

I am experiencing a consistent failure on the connectivity with my webservice connector.

Here is the error message when I perfromed the accout aggregation:

image
image602×318 6.09 KB

However, the account aggregation not always failed per my observation. The connector enables to do 1-2 aggregation per hour for almost 3000 user from the Workday Report (RAAS). If you exceed 2 account aggregations in that hours, you will keep receiving the error message. The test connection will also receive a timeout failure.

*Remark: “healthCheckTimeout”: 999 already in place on the source configuration

However, there is another connector in my tenant is consuming another report endpoint from Workday, they are bothing sharing the same base url, token url and OAuth2.0 credential and similar amount of users will be aggregated. There is no such issue in that connector.

What I just did for testing:
I create a new webservice connector source and place the connection settings and create a HTTP Operation for testing the connection.

  1. If I put the Workday Auth Source Report Context URL there and trigger the test connection, it will fail show timeout consistently.
  2. If I put the another Workday Report Context URL there and trigger the test connection, it will success and never fail in test connection.

Question:

  1. I would like to know whether it is a SailPoint issue or Workday issue?
  2. Why there is such difference between both source but they are consuming the same base url? ( I assmue there is no firewall or network problem since one of them is working well.
  3. I applied an after operation rule (for account aggregation) and account filter on the source config, will that impact the connectivity as above?
  4. How can I fix this connection issue?

Hope to see any response from the expert. Thank you.

Best regards,

Jacky Choi

2

This seems like a Workday issue, possibly rate limiting the report URL itself. If it was a SailPoint issue I would expect any URL used to fail the Test Connection for all of them.

3

But I am not 100% it is a Workday issue since I can spam the report api endpoint thorugh postman, and only SailPoint cant have a consistent account aggregation. Then I am worried that it is no rate limit.

I tried to use VA to run the curl of the report yesterday and I observated such error:
curl: (56) openssl ssl_read: error:0a000126:ssl routines::unexpected eof while reading

Not sure what is the root cause of the problem at the moment…

4

Thanks for you reply :blush: