
To access a Web application, AS ABAP uses the HTTP framework from Internet Communication Manager (ICF) that provides functions for defining the logon procedure. For more information, see Maintaining Logon Procedures.
A simple process is available for configuring the system logon. For more information, see System Logon (ICF system logon application). In addition, you can customize the logon information according to your needs, for example, system ID, client, language, system messages, logon, and system information. For more information, see Configuration Settings.
With this, authentication against an ABAP system reduces to the normal authentication process as is standard for all Web-based applications on an ABAP stack, for example, BSP and Web Dynpro ABAP.
Settings for the Configuration for SSL support are particularly important for security with AS ABAP. For more information, see Configuring the AS ABAP for Supporting SSL. The logon ticket cache function is provided for increasing performance when multiple logons exist.
NWBC uses the Ticket Issuer to log on to the J2EE server. The logon must be properly configured in the J2EE engine for this to work correctly.
Call the SAP NetWeaver Administrator.
Go to Configuration Management.
Choose Authentication.
Select component sap.com/tc~sec~sso~app*ticketissuer.
Enter the following as the assigned login modules:
Login Module Name |
Flag |
|---|---|
EvaluateTicketLoginModule |
SUFFICIENT |
ClientCertLoginModule |
OPTIONAL |
CreateTicketLoginModule |
SUFFICIENT |
BasicPasswordLoginModule |
REQUISITE |
CreateTicketLoginModule |
OPTIONAL |
This may appear as shown in the figure below:
(Ticket Issuer)
SAP Library for SAP NetWeaver on SAP Help Portal at
SAP Library for SAP NetWeaver on SAP Help Portal at
SAP Library for SAP NetWeaver on SAP Help Portal at
SAP Library for SAP NetWeaver on SAP Help Portal at