Integrating a SAML-Enabled Application in the Portal 

Use

When you integrate an application that accepts SAML in the portal, the portal automatically generates the correct URL for accessing the application. The URL includes information such as the SAML artifact, the target URL for the application, and portal-specific information such as the theme used.

Prerequisites

●      The SAML service of the SAP NetWeaver Portal server is running.

●      The portal is set up as a source site as described in Configuring a Portal as a SAML Source Site.

●      The destination site is configured for SAML. If the destination site is hosted by an AS Java, see Configuring AS Java as a Destination Site.

●      If the application is a resource on AS ABAP, a connection between AS ABAP and AS Java must be configured, and the resource must be activated for SAML.

Procedure

...

       1.      In the portal, create a system object for the system on which your target application is running. For more information about creating system objects, see Creating Systems.

Make sure you create a system alias for the system.

For example, for a Web Dynpro application running on an AS Java, create a system object of type R/3 System with Load Balancing.

       2.      Define the connection data for the system. For more information about defining connection data, see Editing Systems.

In the example of a system object for a Web Dynpro application, in the property category Web Application Server, enter data for WAS Host Name and WAS Protocol.

       3.      Define the SAML data for the system as follows:

                            a.      In the property editor of the system object, choose the property category User Management.

                            b.      Enter data in the fields as follows:

Logon Method  = SAML Browser/Artifact

SAML Partner Name = Name of the set of PartnersOutbound parameters for the destination site in the Configuration Adapter. For example, MyDestinationPartner.

                            c.      Save your changes.

       4.      Create an iView for the application and  specify the alias of the system object you created above.

Result

We recommend that before testing you close all browser windows to reset the user context. You can then call up the preview of the iView in the iView editor and access the iView through SAML without having to explicitly provide any form of authentication.

You should assign the iView to a role and assign the role to users as required. For more information on these steps, see the portal documentation at Assigning iViews to Users.