Hi Experts.
We currently have the issue that the URL part after hash character (#) is being removed after SAML authentication when accessing an XS Application.
Example:
https://<system>.hana.ondemand.com/<package>/<subpackage1>/<subpackage3>/#/object/details/<objectid>
If the user is not logged it is redirected for the SAML authentication (accounts.sap.com) and after that the final URL is like following:
https://<system>.hana.ondemand.com/<package>/<subpackage1>/<subpackage3>
We have found that there has been similar issues accessing authentication in backend systems as it is commented at the following SAP Note:
2051210 - Fragments in HTTP URLS are not handled after SAML 2.0 authentication
https://launchpad.support.sap.com/#/notes/2051210/E
Is there a way for fixing or work arounding this issue for an XS Application in HCP?
We have checked the metadata at our SAML Service Provider configuration and the single sign on part is like the following:
<ns2:SingleSignOnService isDefault="true" index="0" Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Location="https://<system>.hana.ondemand.com:443/sap/hana/xs/saml/login.xscfunc"/>
<ns2:SingleSignOnService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect" Location="https://<system>.hana.ondemand.com:443/sap/hana/xs/saml/login.xscfunc"/>
Thanks in advance for your help.
Eduardo
