Migrating to 2.2 Authentication
Problem
You had authentication working, and then you moved to Apache 2.2, and everything is different.
Solution
Authentication was rearchitected in Apache 2.2 to more completely separate authentication and authorization as separate steps which can be configured independently. Although, at first, it can seem to be change for the sake of change, once you understand this separation, the new configuration syntax makes a lot more sense, and the changes that you’ll have to make seem more sensible.
Discussion
These terms—authentication and autorization—are defined in some
detail in the introduction to this chapter. Traditionally, Apache has
blurred the boundary between these two concepts, making it difficult
to configure one without being compelled to configure the other a
particular way. For example, if you wanted to use Digest authentication, you were required to
use a plain text file for the list of users. This is no longer the
case with Apache 2.2.
In order to configure authentication and authorization in Apache 2.2, you’ll need to make three decisions, which, in practical terms, involves choosing one module from each of three lists.
First, you’ll need to determine which authentication type you’re going to use. Your choices are Digest and Basic authentication, so you’ll need to choose either mod_auth_basic or mod_auth_digest. This is done with the AuthType directive, as it was in versions before 2.2:
AuthType Basic
Next, you’ll need to choose your authentication ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access