Defining the Logon Procedure 

Use

You can choose from several different logon procedures when you use a HTTP request to log on to the ABAP AS. You can configure the procedure individually for each service or for an entire service node, including all its services.

Prerequisites

At least one HTTP request handler must have been entered for the service or service node.

Features

·         You can specify for every ICF service what logon procedure must be used to execute it. The following options are available:

                            a.      Standard (default setting): When you log on, multiple checks are run in a specified order.

                            b.      Alternative logon procedure: When you select this option, you can choose the checks yourself, and the order in which they run.

                            c.      Mandatory using logon data: Only the logon data specified in the service (User, Password, Client, and Language) is used to check the logon.

                            d.      Mandatory using client certificate (SSL): The logon can only be performed using X.509 Client Certificate.

You can use only one of these options for each service or service node.

·         If you use the standard or alternative logon procedures, you can use the All Logons checkbox to specify whether the appropriate checks are run (in the specified order) until one of the logon procedures is successful (checkbox activated), or whether the logon is rejected with a message as soon as a logon procedure fails (checkbox not activated).   

·         For each service, you can define an individual response page that appears if the logon fails.

  

Integration

Additional Information

Logon Checks: Overview

Standard Logon Order

Alternative Logon Order

Logojn Using Service Data

Logon with Client Certificate

Logon Using Basic Authentication

Determining the Client

Determining the Logon Language

For information about making ICF communications secure, see the following:

RFC/ICF Security Guide