Configuring SSO with User ID and Password to SAP Systems (SAP Library

Configuring SSO with User ID and Password to SAP Systems

Use

This procedure describes how to configure the Enterprise Portal and a SAP System for Single Sign-On with user mapping. In general we recommend using Single Sign-On with SAP logon tickets or client certificates. Single Sign-On with user ID and password should only be used if no other Single Sign-On method is possible. It has the following advantages:

It can be used for Single Sign-On to SAP Systems that do not support SAP logon tickets (that have a release lower than 4.0B).
You do not have to have Central User Administration (CUA) in place. Users can have a different user ID and password in the SAP System in question than in the reference SAP System used for the logon ticket.

Procedure

Single Sign-On with user ID and password for Java iViews that use Java Connector (JCo)

When you define the JCo destination (RFC connection) to the SAP System, set the attribute LOGONMETHOD to UIDPW. For more information on defining JCo destinations, see Defining JCo Destinations.

Each user must map his or her user ID to his or her user ID in the SAP System as described in Mapping Users: User Enters Own Data.

Single Sign-On with user ID and password for other SAP application types

You can also use Single Sign-On with user ID and password to access the following SAP application types:

Transactions using SAP GUI for HTML, SAP GUI for Java, and SAP GUI for Windows

The SAP GUI for Windows only supports SSO with user ID and password for the structured document technique.

(The structured document technique is the default technique used for running the SAP GUI for Windows in place in the portal and is set in the WinGUI type property of the master iView SAPApplication.Transaction.)

Internet Application Components (IACs)
MiniApps
Business Server Pages (BSPs)
BW reports
Drag&Relate objects

Warning: In the above cases, the user ID and password are transmitted in plain text in the URL. The URL is requested using the HTTP GET method so even using HTTPS is not completely safe. THe URLs containing the user ID and password in plain text can be logged by the Web server or eavesdropped by an external party.

No configuration is necessary.

Result

When the user tries to access the SAP System through the portal, the user mapping information from the portal LDAP directory is used to access the component system