Purpose
The Single Sign-On (SSO) mechanism with user name and password provides an alternative for applications that cannot accept and verify logon tickets. With this SSO mechanism the portal server uses user mapping information provided by users or administrators to give the portal user access to external systems. The portal components connect to the external system with the user’s credentials.
Since the system sends the user's logon ID and password across the network, use a secure protocol such as Secure Sockets Layer (SSL) for sending data.
Process Flow
There are different procedures depending on the requirements.
Single Sign-On to SAP Systems
You can access SAP Systems that do not support logon tickets with SSO with user ID and password. These are SAP Systems with release 3.1I. For more information, see Configuring SSO with User ID and Password to SAP Systems.
Single Sign-On to non-SAP Systems with a Java iView Developed Specifically for the Customer
The system must exist in the system landscape. For more information, see Creating Systems.
The administrator or user must map user data to user data in the system. For more information, see User Mapping.
The iView through which the user tries to access the system must be programmed to get the mapped user data from the data repository and write the user credentials (user ID and password) in a header field of the request. The system can then log on the user with these credentials. This can be done using the Java APIs provided with SAP NetWeaver Portal.
No comments:
Post a Comment