Prerequisites for Using an Arbitrary Mechanism on the Web Server (SAP Library

Prerequisites for Using an Arbitrary Mechanism on the Web Server

To be able to use an arbitrary authentication mechanism that sets the user information in HTTP header variables, your system must meet the following requirements:

The ticket-issuing application server must be at least Release 4.6D, patch level 317.
The ticket-issuing system’s ITS must meet the following release requirements:

Release 4.6D C4, patch level 340 or higher
Release 6.10, patch level 11 or higher
Release 6.20, no patch level requirements

SNC is required for the connection between the AGate and the ticket-issuing application server.

Recommendation

Because the user authentication takes places on the Web server, we also recommend using SNC for the connection between the WGate and the AGate if the ITS installation is a dual host installation.

We also recommend using SNC for the connections to systems that accept logon tickets.

The authentication mechanism must set the user’s ID in an appropriate HTTP header variable.

Each Web server has pre-defined HTTP header variables that it uses for various purposes. For example, the Microsoft Internet Information Server (IIS) and the Apache Web server use the header variable REMOTE_USER to store the user’s ID. The arbitrary authentication mechanism that you use can either set this variable directly or it can use a self-defined one.