Show Contents Previous Page Next Page Chapter 6 - Authentication and Authorization / Access Control, Authentication, and Authorization In contrast to access control, the process of authenticating a remote user is more involved. The question "is the user who he or she claims to be?" sounds simple, but the steps for verifying the answer can be simple or complex, depending on the level of assurance you desire. The HTTP protocol does not provide a way to answer the question of authenticity, only a method of asking it. It's up to the web server itself to decide when a user is or is not authenticated. When a web server needs to know who a user is, it issues a challenge using
the HTTP 401 "Authorization Required" code (Figure 6-1).
In addition to this code, the Figure 6-1. During web authentication, the
server challenges the browser to provide authentication information, and the
browser reissues the request with an Authorization header.
Armed with this information, the browser now issues a second request for the URI, but this time it adds an Authorization field containing the information necessary to establish the user's credentials. (Notice that this field is misnamed since it provides authentication information, not authorization information.) The server checks the contents of Authorization, and if it passes muster, the request is passed on to the authorization phase of the transaction, where the server will decide whether the authenticated user has access to the requested URI.
On subsequent requests to this URI, the browser remembers the user's authentication information and automatically provides it in the Authorization field. This way the user doesn't have to provide his credentials each time he fetches a page. The browser also provides the same information for URIs at the same level or beneath the current one, anticipating the common situation in which an entire directory tree is placed under access control. If the authentication information becomes invalid (for example, in a scheme in which authentication expires after a period of time), the server can again issue a 401 response, forcing the browser to request the user's credentials all over again.
Here's what an unauthorized response looks like. Feel free to try it for yourself.
In this example, we requested the URI /private/
Following the HTTP header is some HTML for the browser to display. Unlike the situation with the 403 status, however, the browser doesn't immediately display this page. Instead it pops up a dialog box to request the user's account name and password. The HTML is only displayed if the user presses "Cancel", or in the rare case of browsers that don't understand Basic authentication.
After the user enters his credentials, the browser attempts to fetch the URI once again, this time providing the credential information in the Authorization field. The request (which you can try yourself) will look something like this:
The contents of the Authorization field are the security scheme,
"Basic" in this case, and scheme-specific information. For Basic authentication,
this consists of the user's name and password, concatenated together and encoded
with base64. Although the example makes it look like the password is encrypted
in some clever way, it's not--a fact that you can readily prove to yourself
if you have the MIME::Base64 module installed:2 Standard Apache offers two types of authentication: the Basic authentication
shown above, and a more secure method known as Digest. Digest authentication,
which became standard with HTTP/1.1, is safer than Basic because passwords are
never transmitted in the clear. In Digest authentication, the server generates
a random "challenge" string and sends it to the browser. The browser encrypts
the challenge with the user's password and returns it to the server. The server
also encrypts the challenge with the user's stored password and compares its
result to the one returned by the browser.3 If
the two match, the server knows that the user knows the correct password. Unfortunately,
the commercial browser vendors haven't been as quick to innovate as Apache,
so Digest authentication isn't widely implemented on the browser side. At the
same time, some might argue that using Basic authentication over the encrypted
Secure Sockets Layer (SSL) protocol is simpler, provided that the browser and
server both implement SSL. We discuss SSL authentication techniques at the end
of this chapter.
Because authentication requires the cooperation of the browser, your options for customizing how authentication works are somewhat limited. You are essentially limited to authenticating based on information that the user provides in the standard password dialog box. However, even within these bounds, there are some interesting things you can do. For example, you can implement an anonymous login system that gives the user a chance to provide contact information without requiring vigorous authentication.
After successfully authenticating a user, Apache enters its authorization phase. Just because a user can prove that he is who he claims to be doesn't mean he has unrestricted access to the site! During this phase Apache applies any number of arbitrary tests to the authenticated username. Apache's default handlers allow you to grant access to users based on their account names or their membership in named groups, using a variety of flat file and hashed lookup table formats.
By writing custom authorization handlers, you can do much more than this.
You can perform a SQL query on an enterprise database, consult the company's
current organizational chart to implement role-based authorization, or apply
ad hoc rules like allowing users named "Fred" access on alternate Tuesdays.
Or how about something completely different from the usual web access model,
such as a system in which the user purchases a certain number of "pay per view"
accesses in advance? Each time he accesses a page, the system decrements a counter
in a database. When the user's access count hits zero, the server denies him
access. Footnotes 1 The three authentication schemes in general
use are Basic, Digest, and Microsoft's proprietary NTLM protocol used by its
MSIE and IIS products. 2 MIME::Base64 is available from CPAN.
3 Actually, the user's plain-text password is
not stored on the server side. Instead, the server stores an MD5 hash of the
user's password and the hash, not the password itself, are used on the server
and browser side to encrypt the challenge. Because users tend to use the same
password for multiple services, this prevents the compromise of passwords by
unscrupulous webmasters. |
