Not able to connect On-premise from Neo Cloud thru cloud connector https call

[former_member585626]

Hi All,

Problem Statement:

Not able to connect On-Premise system from Neo cloud theu cloud connector. We get below error.

javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

Description:

We have requirement of connecting On-Premise (GSAP) system from cloud (Neo) application to post the data thru cloud connector. It was working earlier when we were having TomEE6 and JDK7, when we upgrade to Tomcat8 and JDK8, we must do the code change to make HTTP connection using HTTP url connection library instead of HTTP client which is from Destination configuration of cloud.

Technologies used Earlier:

JDK7, TomEE7, HTTP client derived from Destination factor library

Technologies using Now:

JDK8, Tomcat8, Http URL connection (explicit) not from destination factory, we read destination details using configuration library.

[AntalP]

Hi Mohan,

Between SCP Neo application and on-premise cloud connector you need to define an HTTP URL not HTTPS. The HTTP traffic is encrypted already with TLS in the VPN tunnel.

Where do you receive the SSL handshake error, in Neo application or in cloud connector?

What is the proxy type in Neo HTTP destination on-premise or internet?

Best regards,

Antal

[former_member585626]

Hi Antal,

Thanks for quick reply,

PFB the details of Destination. We defined HTTP only not Https. The on-premise application exposes the API with Https, you could see in below url. We get SSL handshake error when we invoke the on-premise url from Neo application. The call is not reached to cloud connector, i believe the issue is in between neo application and cloud connector. The proxy type is On-premise.

[former_member585626]

Hi Antal,

As you suggested, i reviewed the code it is as per the below documents.

For Tomcat:(We modified according to this post)

https://help.sap.com/viewer/cca91383641e40ffbe03bdc78f00f681/Cloud/en-US/474eae1b69c9434b9dce0314b8d...

For Tom EE: (This is Existing – we had code same like below)

https://help.sap.com/viewer/cca91383641e40ffbe03bdc78f00f681/Cloud/en-US/e76f9e75bb571014a7218bcd30a...

As per the document, In case of Tomcat, we should use the proxy for connecting On-premise system, the value returns as below. This is a proxy for On-premise only.

HC_OP_HTTP_PROXY_HOST == localhost

HC_OP_HTTP_PROXY_PORT == 20005

When i have above proxy in place, i get below error

Unable to tunnel through proxy. Proxy returns "HTTP/1.1 405 Method Not Allowed

If i have other proxy for Ex: Internet Proxy

http.proxyHost == proxy

http.proxyPort == 8080

I still face SSL handshake issue.

SSL Handshake is an exception while connecting the target URL, 405 method not allowed is an exception after connecting wwhen i try to read the response.

Thanks.

[former_member585626]

Hi

As per Neo cloud platform team suggested, modified the url from Https protocol to Http protocol then we get 503 service unavailable. the ssl issue might e resolved. Again added one more property to find out connector's location Id,

urlConnection.setRequestProperty("SAP-Connectivity-SCC-Location_ID", "OP_SCC_*****_Development_Env");

The the error turned to 404 Not found.