SAML2 service not accessibleWhat has happened?Calling of URL https://myxxxx.scmibp1.ondemand.c

[Azza]

SAML2 service not accessible

What has happened?

Calling of URL https://myxxxx.scmibp1.ondemand.c was terminated during SAML2 processing

 Note

• No RelayState mapping found for RelayState value oucxzzvvwvaoewtboreefozabfoyazwwzyeawuw

HTTP 404 Not Found

© 2001-2024, SAP SE

[vincentverheyen]

Hi Azza,

If the below doesn't help, feel free to provide some further context on the environments. How are you trying to call exactly? Using a proxy server? Web dispatcher?

One general remark/requirement is that end-users need to access the Service Provider in the same way that the Identity Provider itself will contact it when sending the SAML 2.0 response (use the same host name, protocol and port).

For example, you might experience the error due to any of the following mismatches:

• Different hosts: Access Service Provider using https://host:port/yourapp but in Identity Provider configuration, Assertion Consumer Service endpoint is https://anotherhost:port/sap/saml2/sp/acs/XXX.
• Different ports: Access Service Provider using https://host:port/yourapp but in Identity Provider configuration, Assertion Consumer Service endpoint is https://host:anotherport/sap/saml2/sp/acs/XXX.
• Different protocols: Access Service Provider using http://host:port/yourapp but in Identity Provider configuration, Assertion Consumer Service endpoint is https://host:port/sap/saml2/sp/acs/XXX.

If the protocol, host or port is different, it is necessary to export the metadata file once more, using the same protocol, host and port in the URL which is used to access the protected resource, then import the metadata to the Identity Provider once again.

[Azza]

The System working on many computer normally except my laptop it gaves this error message