Rest Receiver Adapter

[former_member264514]

Hi guys,

i have a problem with rest receiver adapter in SAP PI 7.4 single stack version. Endpoint is awaiting a header field for authorization. So i put in "HTTP Headers" the following value:

URL-Pattern: 

I'm using Proxy.

Error i receive:

With postman app call is working. Here if i not sending header key i receive same "Forbidden" error.  Now i have no idea whats wrong.

Has anyone ideas?

Regards,

Marcus

[former_member264514]

The postman payload and header settings are correct. The data format was also correct.

I think i have found the error. We had some mistake in firewall configuration. Now i'm fighting with handshake error.

[former_member186851]

Ok Marcus,let us know the status.

[engswee]

Hi Marcus

In addition to what the others have mentioned here, I'd definitely recommend that you have XPI Inspector in your system. It comes in very handy to troubleshoot such issues as yours as there are more details in the logs.

For handshake issues, you can refer to my blog below on using XPI inspector to troubleshoot it.

Rgds

Eng Swee

[former_member264514]

Hi Eng,

thanks for blog. i'm already using XPI Inspector. Below is the result. For me looks like CONNECT is established but POST gives handshake error. Now i have no idea because with this endpoint it works in Postman without any SSL settings.

Anyone an idea?

[former_member186851]

Marcus,

Postman testing is different.

With respect to PI you need to enable port and some connections should be maintained to connect and post.

[former_member264514]

Hi Raghuraman,

can you please concretize your answer? I have configured rest adapter channel and if there i set ignore all exceptions in error handling it works fine.

Regards,

Marcus

[engswee]

Hi Marcus

From the description of your logs it looks like it's trying to establish HTTPS connection as it's using the common HTTPS 443 port.

Can you try running the XPI inspector test as described in my blog and post the IAIK/SSL debug log here? That would provide more insight into the reason for the handshake failure.

Rgds

Eng Swee

[former_member264514]

Hi Eng,

here is the log. What do you mean with "it's using the common https 443 port"?

Regards,

Marcus

[engswee]

Hi Marcus

By default, HTTPS uses port 443. I noticed in your logs that port 443 is used, so that's why my guess is that you are transmitting on HTTPS instead of HTTP.

However, from the debug log, it is unusually short for an SSL debug log. Maybe the server really does not accept HTTPS the way you mentioned how SOAP UI does not require it.

Can you share a screenshot of your configuration of the communication channel, in particular the section regarding URL or target host?

Rgds

Eng Swee

[former_member264514]

Hi Eng,

here the screenshots:

[engswee]

Hi Marcus

When you test using POSTman, do you use https too for the endpoint?

Rgds

Eng Swee

[former_member264514]

Yes also in POSTman

[engswee]

Can you check with the server team which version of SSL/TLS do they support?

[former_member264514]

Hi Eng,

at the moment i check some things with server team. Could be that SAP/Proxy not supports SNI (Server Name Indication https://en.wikipedia.org/wiki/Server_Name_Indication).

Regards,

Marcus

[engswee]

Hi Marcus

That's something interesting. I haven't encountered SNI before. If the server team confirms that this is required, maybe it's worth opening a call with SAP to check if that is supported.

Rgds

Eng Swee

[maheswarareddykonda]

hi Marcus,

can you try add proxy user and password in channel?

[former_member264514]

Hi Maheswarareddy,

proxy of our service provider doesn't need any user/password settings so i can't fill this data.

Regards,

Marcus

[maheswarareddykonda]

actually long back we got handshake issue, that time we had to add those credentials in production environment, though in DEV and QA we able to test with out those credentials.

so i thought you have to use that.

[iaki_vila]

Hi Marcus,

The forbidden error is raised when the server can't understand the http call and it can't find the authentication or there are something issue with the structure or the data.

Try to confirm:

- All the http headers

- Try to respect the case sensitive in the http headers and their values comparing Postman APP

- Payload as Raghuraman said.

Regards.

[former_member186851]

Hello Marcus,

Can you post the payload your using the Postman APP?

Are you adding custom headers over there as well?