Документ взят из кэша поисковой машины. Адрес
оригинального документа
: http://www.arcetri.astro.it/manual/fr/mod/mod_auth_basic.html
Дата изменения: Fri Nov 20 00:43:57 2015 Дата индексирования: Sun Apr 10 08:01:52 2016 Кодировка: Поисковые слова: п п п п п п п п п п п п п п п п п п п п п п п п п п п п п п п п п п п п п п |
Apache HTTP Server Version 2.4
Description: | Basic HTTP authentication |
---|---|
Status: | Base |
Module Identifier: | auth_basic_module |
Source File: | mod_auth_basic.c |
Compatibility: | Available in Apache 2.1 and later |
This module allows the use of HTTP Basic Authentication to
restrict access by looking up users in the given providers.
HTTP Digest Authentication is provided by
mod_auth_digest
. This module should
usually be combined with at least one authentication module
such as mod_authn_file
and one authorization
module such as mod_authz_user
.
Description: | Sets whether authorization and authentication are passed to lower level modules |
---|---|
Syntax: | AuthBasicAuthoritative On|Off |
Default: | AuthBasicAuthoritative On |
Context: | directory, .htaccess |
Override: | AuthConfig |
Status: | Base |
Module: | mod_auth_basic |
Normally, each authorization module listed in AuthBasicProvider
will attempt
to verify the user, and if the user is not found in any provider,
access will be denied. Setting the
AuthBasicAuthoritative
directive explicitly
to Off
allows for both authentication and
authorization to be passed on to other non-provider-based modules
if there is no userID or rule
matching the supplied userID. This should only be necessary when
combining mod_auth_basic
with third-party modules
that are not configured with the AuthBasicProvider
directive. When using such modules, the order of processing
is determined in the modules' source code and is not configurable.
Description: | Fake basic authentication using the given expressions for username and password |
---|---|
Syntax: | AuthBasicFake off|username [password] |
Default: | none |
Context: | directory, .htaccess |
Override: | AuthConfig |
Status: | Base |
Module: | mod_auth_basic |
The username and password specified are combined into an Authorization header, which is passed to the server or service behind the webserver. Both the username and password fields are interpreted using the expression parser, which allows both the username and password to be set based on request parameters.
If the password is not specified, the default value "password" will be used. To disable fake basic authentication for an URL space, specify "AuthBasicFake off".
In this example, we pass a fixed username and password to a backend server.
<Location /demo> AuthBasicFake demo demopass </Location>
In this example, we pass the email address extracted from a client
certificate, extending the functionality of the FakeBasicAuth option
within the SSLOptions
directive. Like the FakeBasicAuth option, the password is set to the
fixed string "password".
<Location /secure> AuthBasicFake %{SSL_CLIENT_S_DN_Email} </Location>
Extending the above example, we generate a password by hashing the email address with a fixed passphrase, and passing the hash to the backend server. This can be used to gate into legacy systems that do not support client certificates.
<Location /secure> AuthBasicFake %{SSL_CLIENT_S_DN_Email} %{sha1:passphrase-%{SSL_CLIENT_S_DN_Email}} </Location>
<Location /public> AuthBasicFake off </Location>
Description: | Sets the authentication provider(s) for this location |
---|---|
Syntax: | AuthBasicProvider provider-name
[provider-name] ... |
Default: | AuthBasicProvider file |
Context: | directory, .htaccess |
Override: | AuthConfig |
Status: | Base |
Module: | mod_auth_basic |
The AuthBasicProvider
directive sets
which provider is used to authenticate the users for this location.
The default file
provider is implemented
by the mod_authn_file
module. Make sure
that the chosen provider module is present in the server.
<Location /secure> AuthType basic AuthName "private area" AuthBasicProvider dbm AuthDBMType SDBM AuthDBMUserFile /www/etc/dbmpasswd Require valid-user </Location>
Providers are queried in order until a provider finds a match for the requested username, at which point this sole provider will attempt to check the password. A failure to verify the password does not result in control being passed on to subsequent providers.
Providers are implemented by mod_authn_dbm
,
mod_authn_file
, mod_authn_dbd
,
mod_authnz_ldap
and mod_authn_socache
.