User Guide

Table Of Contents
About user security 379
About web server authentication
All major web servers support basic HTTP authentication. Some web servers also support other
authentication methods, including Digest HTTP authentication and Microsoft NTLM
authentication.
Note: Macromedia Dreamweaver MX and Studio MX do not support NTLM security with RDS.
Therefore, you cannot use RDS with these applications if the ColdFusion RDS servlet (cf_root/
CFIDE/main/ide.cfm) is in a directory that is protected using NTLM security.
In web server authentication, the web server requires the user to log in to access pages in a
particular directory, as follows:
1.
When the user first requests a page in the secured directory, the web server notifies the browser
that the requested page requires credentials (a user ID and password).
Basic HTTP authentication sends the user ID and password in a base64-encoded string with
each request. Use SSL (Secure Sockets Layer) for all page transactions, to protect the user ID
and password from unauthorized access. For more information on SSL and the keytool utility,
see About LDAP Server Security” on page 544.
2.
The browser prompts the user for the credentials.
3.
The user supplies the credentials and the browser send the information back to the web server
along with the original request.
4.
The web server checks the user ID and password, using its own user authentication mechanism.
5.
If the user logs in successfully, the browser caches the authentication information and sends it
in an HTTP Authorization header with every subsequent page request from the user.
6.
The web server processes the requested page and all future page requests from the browser that
contain the HTTP Authorization header, if it is valid for the requested page.
You can use web server authentication without using any ColdFusion security features. In this
case, you configure and manage all user security through the web server’s interfaces.
You can also use web server authentication with ColdFusion application authentication, and thus
you can use ColdFusion security for authorization. If the web server uses basic HTML
authentication, the ColdFusion
cflogin tag provides access to the user ID and password that the
user entered to log in to the web server. If the web server uses Digest or NTLM authentication,
the
cflogin tag normally gets the user ID, but not the password.
As a result, your application can rely on the web server to authenticate the user against its user and
password information, and does not have to display a login page. You use the
cflogin and
cfloginuser tags to log the user into the ColdFusion user security system, and use the
IsUserInRole and GetAuthUser functions to ensure user authorization. For more information
on this form of security, see A web server authentication security scenario” on page 386.
Note: If a user has logged in using web server authentication and has not logged in using ColdFusion
application authentication, the
GetAuthUser tag returns the web server user ID. You could use this
feature to combine web server authentication with application authorization based on the user’s ID.