Configuring a Portal Server for
SSO with Logon Tickets
The following scenarios exist:
● The portal is the ticket-issuing system
By default the SAP NetWeaver Portal is configured so that the underlying SAP NetWeaver Application Server (AS) Java issues logon tickets, therefore you do not need to make any changes.
By default
the authentication scheme used by the portal references a login module stack
that issues and accepts tickets. For more information, see
Defining an
Authentication Scheme and
Adjusting the Login
Module Stacks for Using Logon Tickets.
● Another system is the ticket-issuing system
You must
configure the portal to accept the tickets issued by another system. This
takes place in the underlying AS Java. For more information, see
Configuring the AS
Java to Accept Logon Tickets.
In addition, there are some settings that you need to make in particular cases. These are described below.
In Add-In
installations, the logon tickets of the AS Java and AS ABAP must be different.
Change the client that is written to the logon ticket. For more information,
see
Specifying
the AS Java Client to Use for Logon Tickets.
For more
information, see
Configuring the
Validity Period of Logon Tickets.
If users’
portal user IDs are different to their user IDs in the component systems, the
administrator or user must map the portal user ID to the user ID in the other
systems. You must define a reference system for user data and map the portal
users to the users in this system. For more information, see Defining an SAP
Reference System for User Data and
User
Mapping.
SAP Systems only: Set logon method to Logon tickets in portal system landscape
For each SAP System that the portal accesses using the Java Connector (JCo), do the following to enable access with logon tickets:
...
1.
Open the system for
property editing as described in
Editing SAP System
Properties.
2. Set the value of the property Logon Method to SAPLOGONTICKET.
3. Save your changes.