3221790 - SAML2: New trusted provider can not be saved

• Adding new trusted provided by uploading IdP metadata, below error message shows in SAML configuration page: 
  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...

• SAP NetWeaver
• SAP NetWeaver Application Server for SAP S/4HANA
• ABAP PLATFORM - Application Server ABAP

ABAP platform all versions ; SAP NetWeaver Application Server for ABAP all versions ; SAP NetWeaver Application Server for SAP S/4HANA all versions ; SAP NetWeaver all versions ; SAP Web Application Server for SAP S/4HANA all versions

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