You have a SAML 2.0 identity provider and service provider in your landscape.
You have configured your legacy systems to accept logon tickets.
Ideally, the user IDs of users on the service provider are identical to their user IDs on the legacy systems. If not, you must configure user mapping.
For more information about configuring the communication between AS ABAP and AS Java, from the SAP NetWeaver documentation choose .
Not all releases of SAP software support Security Assertion Markup Language (SAML) 2.0. These systems can still benefit from having SAML 2.0 in the system landscape. Configure your service provider to issue logon tickets when a user logs on. This enables legacy systems within the domain to perform Single Sign-On initiated by the SAML 2 authentication.