Show TOC

Configuring Single Sign-On with SAML Token ProfilesLocate this document in the navigation structure


Security Assertion Markup Language (SAML) is a standard that defines a language to exchange security information between partners. The SAML standard is driven by the Organization for the Advancement of Structured Information Standards (OASIS). SAML uses assertions that contain statements about a subject, authentication, authorization and attributes.

SAML Token Profile is developed by the OASIS Web Services Security (WS Security) Technical Committee as a standard to integrate and use SAML for Web Services Security.


Although both the SAML token profile and SAML browser artifact use the SAML standard for transferring security information, they are used for different authentication purposes, as shown below:

  • SAML browser artifacts are used for authenticating Web-based access from a Web browser. More information about using SAML browser artifacts in SAP NetWeaver: Using SAML Browser Artifacts .

  • You use SAML token profiles for WS access authentication at the SOAP message level.

  • SAML Trust Relationship

    You have set up a SAML 2.0 trust relationship and, in report WSS_SETUP, have selected the option Use SAML 2 Trust Relationship (more information: Preparing the WS Provider AS ABAP for Accepting SAML Token Profiles for Validation with the SAML 2 Infrastructure und Message-Based Authentication with WS-Security ).


    If you use the SAML trust relationship, the system uses the SAML 2 PSE (SAML 2 Personal Security Environment) for signing locally-issued tokens.

  • Ticket Trust Relationship

    You have set up a trust relationship between the WS issuer and the WS consumer system. If you have configured your systems for using logon tickets and, in report WSS_SETUP, have selected the option Use Logon Ticket Trust Relationship , this trust relationship has already been set up.


    By default, the system PSE, which is based on the Digital Signature Algorithm (DSA), is used for logon ticket configuration. This means that you cannot use this PSE if you want to send encrypted responses.

    Note that:

    In AS ABAP and AS Java, you can use a certificates other than the client's signature certificate (which is based on the system PSE with DSA) for encryption by the provider.

    If you do not want to configure your systems for the use of logon tickets, set up the required trust relationship between systems, as described in Configuring a Trust Relationship for SAML Token Profiles Without Logon Ticket Configuration .


SAP NetWeaver Application Server ABAP enables you to use the sender-vouches and holder-of-key subject confirmation methods to confirm a subject with SAML token profile authentication.

If you have selected symmetric signature and encryption for connection security in the AS ABAP, use the holder-of-key method. For all other connection security mechanisms, use sender-vouches.