How to call Principal propagated destination from Java on SAP Cloud Platform?

[former_member564484]

I am trying to call a Destination of ECC from java, whose Authentication type is Principal Propagation and all the Configurations from ECC side and SAP Cloud Platform side are proper. The destination call is working from UI5 application and Mobile application. When i am trying to call the same destination from Java, i am getting 'HTTP/1.1 405 Method Not Allowed'.

SAP has given a document where they used SAP Tomcat 8 SDK version 1.43.20. But the recent version of SDK is 3.67.10 in which all the APIs used in their help document are removed. So we used the new APIs provided and tried calling destination but that's giving 405.

Help Document Link: SAP Help Destination

Did anyone face similar issue? Please help us with resolving this issue.

[gregorw]

Have you checked in the Cloud Connector that the Java Application is trusted for Principal Propagation?

[former_member564484]

Yes, Java Application is trusted for Principal Propagation. For a reference some Screenshots has been attached.

trustapplication.png

principalprop.png

[Ivan-Mirisola · Accepted solution]

Hi Neelam,

It would be nice if you shared the complete exception thrown by your Java application while calling the destination. It is also important to figure out how you have setup the security in your application.

BTW: Web Tomcat 8 runtime uses the ConnectivityConfiguration API instead of HTTPDestination API.

Please check that you are in fact using the correct API and that your application is requesting authentication from your SCP Account.

Furthermore, you need to make sure your request in Java is built in a way that it forwards the principal to be propagated into the Could Connector for further processing/mapping into your on-premise system.

Best regards,
Ivan

[former_member605676]

Hello Neelam,

Could you please let me know what configuration you did to resolve this problem.

Actually I'm also facing same issue and I don't know how to resolve.

Thanks & Regards,

Shivakumar

[former_member564484]

Hi Ivan,

We figured out the issue. It was a configuration in Cloud connector, so we fixed the issue.

Thank You

Regards
Neelam

[Ivan-Mirisola]

Could you please share your solution so others can benefit when facing similar issues?