Skip to Content

Error while configuring https in pi 7.3 dual stack: Urgent Plz help

Sep 12, 2017 at 01:36 AM


avatar image

I am listing everything i have done till toady in PI .

1) Implemented all steps as per below link.

1.1) imported certificate in below order

a) PI Dev Certificate

b) Root Certificate

2) set port 50001 in exchange profile for all https parameters and deleted 50000 from existing http profile.

3) set below parameters in ICM; restarted pi system and hence all http is now redirecting to https. icm/HTTP/redirect_0 = PREFIX=/, FROM=*, FROMPROT=http, PROT=https,, PORT=50001

Problem/Error: When double click on channel in PI i am getting below error.

Inline image 1

Inline image 2


10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

4 Answers

Best Answer
Shashi Bhushan Oct 02, 2017 at 12:08 PM

Issue resolved by importing certificate in right order. root --intermediate and server certificate.

also import the certificate in trusted ca.

10 |10000 characters needed characters left characters exceeded
Jens Schwendemann Sep 12, 2017 at 06:49 AM

Unfortunately the inline Images are not visible. Could you please try again?

10 |10000 characters needed characters left characters exceeded
Shashi Bhushan Sep 12, 2017 at 07:22 AM

Attempt to access application REPOSITORY using HTTP Method Invocation (HMI) failed. Detailed information: Invoking ROA method "ReadObjects" via HMI ... FAILED due to following exception: Message: Connection to system REPOSITORY using application REPOSITORY lost. Detailed information: Error receiving http response from URL "https://XYZ.A.B.C:50001/rep/remoteobjectaccess/int?container=ejb"! Details: caught exception Message: Peer certificate rejected by ChainVerifier Stacktrace: org.w3c.www.protocol.http.HttpException: Peer certificate rejected by ChainVerifier Peer certificate rejected by ChainVerifier at Source) at Source) at Source) at Source) at Source) at Source) at Source) at org.w3c.www.protocol.http.HttpBasicConnection.a(SourceFile:459) at org.w3c.www.protocol.http.HttpBasicServer.getConnection(SourceFile:446) at org.w3c.www.protocol.http.HttpBasicServer.runRequest(SourceFile:1208) at org.w3c.www.protocol.http.HttpManager.runRequest(SourceFile:1141) at org.w3c.www.protocol.http.HttpURLConnection.connect(SourceFile:235) at at at at at at at at at at at at at at at at at at at sun.reflect.GeneratedMethodAccessor598.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke( at java.lang.reflect.Method.invoke( at at at

10 |10000 characters needed characters left characters exceeded
Evgeniy Kolmakov Sep 12, 2017 at 08:50 AM

Hi Shashi!

...The main reasons for this error could be checked in the steps below:

1. The correct server certificate could not be present in the TrustedCA

keystore view of NWA. Please ensure you have done all the steps described in these two URLs:

Security Configuration at Message Level

2. The server certificate chain contains expired certificate. Check for

it (that was the cause for other customers as well) and if it's the case

renew it or extend the validation.

3. Some other customers have reported similar problem and mainly the

problem was that the certificate chain was not in correct order. Basically the server certificate chain should be in order

Own->Intermedite->Root. To explain in detail, if your server certificate is A which is issued by an intermediate CA B and then B's certificate is issued by the C which is the root CA (having a self signed certificate).

Then your certificate chain contains 3 elements A->B->C. So you need to have the right order of certificate in the chain. If the order is B first followed by A followed by C, then the IAIK library used by PI

cannot verify the server as trusted. Please generate the certificate in the right order and then import this certificate in the TrustedCA keystore view and try again. Please take this third steps as the principal one.

As a resource, you may need to create a new SSL Server key.

The requirement from SAP SSL client side is that the requested site has to have certificate with CN equal to the requested site. I mean if I request URL X then the CN must be CN=X.

In other words, the CN of the certificate has to be equal to the URL in the ftp request. This can be the IP address or the full name of the host.

Request the url with the IP of the SSL Server and the certificate to be with CN = IP of the server.

In any other case the SSL communication will not work.

Hope the information help!...

Some people say that even restarting the server could help.

Regards, Evgeniy.

Show 1 Share
10 |10000 characters needed characters left characters exceeded

Retarding this sequence. I talked to the the person who sent me signed certificate. He said he has no intermediate certificate . he said i uploaded the certificate/private key (generated by pi) and he got the public key. so he sent me only two file

1) certificate and

2) root certificate

So i uploaded first and then 2nd.

I think i am right ?