Configuring a Reference System for User
Mapping
When you use logon tickets for Single Sign-On (SSO) to ABAP-based systems, users must have the same user IDs in all ABAP-based systems that are configured to use logon tickets. If the ABAP user IDs are different from the portal user IDs, you must define a reference system. Users then map their portal user ID to the user ID in the reference system.
The mapped user ID is included in the logon ticket and enables SSO using logon tickets to all ABAP systems in which the user has the same user ID.
● Users have the same ID in all ABAP systems that are configured to use logon tickets for SSO. Passwords do not have to be identical.
● The system you want to use as a reference has been defined as a system object in the SAP NetWeaver Portal.
The system must exist in the system landscape of the portal and have a system alias.
○
For more
information about creating as system object, see
Creating
Systems.
○
For more
information about system aliases, see
Maintaining a System Alias
List.
● This procedure requires you to restart the SAP NetWeaver Application Server (AS) Java, so you should plan for the required downtime while the AS Java restarts.
...
1. Set the user mapping properties.
You must always set a value for the property User Mapping Type.
For more
information, see
System
Properties for User Mapping.
2. Start User Management Configuration.
For more
information, see
Configuring User
Management.
3. Choose the User Mapping tab.
4. In Reference System, select the system alias of the ABAP-based system.
5. Restart the AS Java.
When users start the user mapping function, one of the component systems that they can select is the reference system. They can map their portal user ID to their user ID in this reference system. To map users, use one of the following processes:
●
Mapping
Users: Administrator Tool
●
Mapping
Users: User Enters Own Data
The user mapping function connects to the reference system using the user ID and password to verify that the password entered by the user is correct. The next time the user logs on to the portal, the portal generates a logon ticket for the user that contains both his or her portal user ID and mapped user ID.