Paradyne OpenLane SLM 5.5 - Manual (Page 43)

7800-A2-GB32-00 January 2002 5-1
5
Apache User Access Authentication
User Access Authentication
User access authentication is used to specify who has access to the Web server.
When authentication is enabled on the Web server, it affects all users of the
system.
There are many mechanisms that can be used to set user access. HyperText
Transfer Protocol (HTTP) Challenge/Response is presented here. You can choose
another authentication mechanism or a combination of methods, as long as the
authentication mechanism provides the REMOTE_USER environment variable to
CGI programs. Methods and protocols include:
T HTTP Challenge/Response
T SSL (Secure Sockets Layer)
T Secure HTTP with a well-configured firewall
T VPN (Virtual Private Network)
T A router
The following are requirements of Apache user access authentication under
OpenLane:
T The Customer ID and username must match.
T Authentication is either enabled or disabled for all customer IDs. If
authentication is enabled, every customer ID must have an associated user
with a username.
T There can only be one username per Customer ID for authentication.
When authentication is enabled, the first OpenLane Login page displays a Log In
button instead of an Enter your Customer ID prompt. Clicking on the button
invokes a window for entering User Name and Password.