Test connection failing in web services connector

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

Hi @baoussounda ,

I couldn’t see the certificate when I ran this command on the VA. However, I’m able to see the certificate when I run the same command in Bash.

I got the following response when I ran it on the VA:

Connecting to *******

CONNECTED(00000003)
write:errno=104

no peer certificate available

No client certificate CA names sent

Negotiated TLS1.3 group:

SSL handshake has read 0 bytes and written 1561 bytes

Verification: OK

New, (NONE), Cipher is (NONE)

Protocol: TLSv1.3
This TLS version forbids renegotiation.
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
Verify return code: 0 (ok)

23

Verify the endpoint using postman.

  • If it works in postman, compare:
  • Base URL and Context URL
  • HTTP method
  • Headers - content-Type and Authorization
  • Authentication configuration
  • Request body and query parameters

Check for SSL/TLS certificate, network/firewall restriction. If endpoint is reachable from VA

Review connector logs for exact HTTP response .

24

Hi @sandy_sandy

Can you perhaps see if the server you are trying to connect to is on-prem server. In that case, you may need to add this host into no_proxy configuration in Proxy.yaml file on VA. Can you please check if that helps.

Note that if there are some redirectional URLs being used for authentication, then you may need to add them as well into no_proxy configuration.

Regards

Vikas.