Web server plug-in remote user information processing
You can configure your web server with a vendor-acquired authentication module and then configure the web server plug-in to route requests to an application server.
If an application calls the getRemoteUser method, it relies on
a private HTTP header that contains the remote user information and
is parsed by the plug-in. The plug-in sets the private HTTP header
value whenever a web server authentication module populates the remote
user in the web server data structure. If the private HTTP header
value is not set, the call to getRemoteUser method by the application
returns a null value.
- In the case of an Apache Web Server or the IBM® HTTP Server, the plug-in builds the private header from the information contained in the associated request record.
- In the case of a Sun One Web Server, the plug-in builds the private header from the information contained in the auth_user property associated with the request. The private header is usually set to the name of the local HTTP user of the web browser, if HTTP access authorization is activated for the URL.
- In the case of a Domino® Web Server, the plug-in builds the private header from the information contained in the REMOTE_USER environment variable. The plug-in sets this variable to anonymous for users who have not logged in and to the username for users who are logged into the application.
- In the case of an Internet Information Services (IIS) Web Server, the plug-in builds the private header from the information contained in the REMOTE_USER environment variable. The plug-in sets this variable to the name of the user as it is derived from the authorization header sent by the client.

