SAP Knowledge Base Article - Preview

3221790 - SAML2: New trusted provider can not be saved

Symptom

  • Adding new trusted provided by uploading IdP metadata, error shows: 
    New trusted provider can not be saved. You can get more information by collecting traces using tool http(s)://host:port/sap/bc/webdynpro/sap/sec_diag_tool?sap-client=XXX

And

  • SAML trace shows error: 
    SAML20 SP (client XXX ): Certificate for metadata verification is considered to be binary.
    SAML20 SP (client XXX ):  Exception raised:
    SAML20  SAML20 CX_SAML20_CORE: An exception was raised. Long text: An exception was raised. 
    SAML20     at CL_SAML20_ENTITY->SAVE_CERTIFICATES_IN_PSE(Line 70)
    SAML20     at CL_SAML20_ENTITY->SAVE_ENTITY(Line 433)

SAML 2.0 traces can be captured using with the KBA 2960670.


Read more...

Environment

SAP Netweaver ABAP server

Product

ABAP platform all versions

Keywords

New trusted provider, New Trusted Identity Provider, can not be saved, Metadata Verification, binary certificate, SAML 2.0 Configuration, SAML2 Configuration, SAML configuration, Upload Metadata File , KBA , BC-SEC-LGN-SML , SAML 2.0 for ABAP , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.