cancel
Showing results for 
Search instead for 
Did you mean: 

ApptoAppSSO destination to HANA XS: Unable to verify XML signature

Former Member

Hello,

I am attempting to connect a HANA XS application to an HTML5 application in HCP. My case is close to the one in this guide:

https://blogs.sap.com/2016/03/21/principal-propagation-between-html5-and-sap-hana-xs-on-sap-hana-clo...

I have set the following destination:

Only difference is that I am using SAP's default SSO. I have no issues connecting to the HANA XS service directly and authenticating. When the app tries to connect through the destination, the connection fails.

In the browser debugger I see the following error returned to the app:

StatusCode in ResponseMessage != OK; please refer to the database trace for more information

In the server log I get the following:

Assertion authentication failed with reason: Unable to verify XML signature(StatusCode: , StatusMessage: )

What can be the reason, is there an issue with the destination configuration I set?

Accepted Solutions (0)

Answers (4)

Answers (4)

SebastianEsch
Active Participant
0 Kudos

In our case we had the same problem on a HANA instance in HCP with SP11. After an upgrade to SP12 it worked as expected. Now we have an AppToAppSSO connection from one HCP Account where we are running the HTML5 App to another HCP Account where the HANA instance is located.

SebastianEsch
Active Participant
0 Kudos

In our case we had the same problem on a HANA instance in HCP with SP11. After an upgrade to SP12 it worked as expected. Now we have an AppToAppSSO connection from one HCP Account where we are running the HTML5 App to another HCP Account where the HANA instance is located.

Former Member
0 Kudos

It works fine in one HCP account, but not in another. One account has a HANA version 1.00.102.04.1453734118 (SPS 10). There the destination works with no issues.

In another account, the HANA version is 1.00.112.05.1469552341 (SPS 11).

There we have the following issue. The user is recognized, but the HTTP request returns code 403 - Forbidden. If the same service is called directly from a browser, it works fine, so it doesn't seem to be due to a lack of rights. If the user is not present in HANA, it is created and then we get status code 500.

Former Member
0 Kudos

Turns out I needed to add the HCP service provider settings as an identity provider in HANA. After adding a SAP Cloud Identity IdP, I did just that and it worked.

0 Kudos

Hi Tsvetelin,

I have the same issue as you. Can you please share some details how excactly you solved the issue?

Thank you.

Christian