summaryrefslogtreecommitdiffstats
path: root/docs/manual/howto/auth.html
diff options
context:
space:
mode:
authorDaniel Baumann <daniel.baumann@progress-linux.org>2024-04-27 06:33:50 +0000
committerDaniel Baumann <daniel.baumann@progress-linux.org>2024-04-27 06:33:50 +0000
commitfe39ffb8b90ae4e002ed73fe98617cd590abb467 (patch)
treeb80e5956907d8aeaaffe4e4f0c068c0e6157ce8b /docs/manual/howto/auth.html
parentInitial commit. (diff)
downloadapache2-fe39ffb8b90ae4e002ed73fe98617cd590abb467.tar.xz
apache2-fe39ffb8b90ae4e002ed73fe98617cd590abb467.zip
Adding upstream version 2.4.56.upstream/2.4.56upstream
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to '')
-rw-r--r--docs/manual/howto/auth.html25
-rw-r--r--docs/manual/howto/auth.html.en640
-rw-r--r--docs/manual/howto/auth.html.es717
-rw-r--r--docs/manual/howto/auth.html.fr.utf8681
-rw-r--r--docs/manual/howto/auth.html.ja.utf8692
-rw-r--r--docs/manual/howto/auth.html.ko.euc-kr355
-rw-r--r--docs/manual/howto/auth.html.tr.utf8639
7 files changed, 3749 insertions, 0 deletions
diff --git a/docs/manual/howto/auth.html b/docs/manual/howto/auth.html
new file mode 100644
index 0000000..5e5578d
--- /dev/null
+++ b/docs/manual/howto/auth.html
@@ -0,0 +1,25 @@
+# GENERATED FROM XML -- DO NOT EDIT
+
+URI: auth.html.en
+Content-Language: en
+Content-type: text/html; charset=UTF-8
+
+URI: auth.html.es
+Content-Language: es
+Content-type: text/html; charset=ISO-8859-1
+
+URI: auth.html.fr.utf8
+Content-Language: fr
+Content-type: text/html; charset=UTF-8
+
+URI: auth.html.ja.utf8
+Content-Language: ja
+Content-type: text/html; charset=UTF-8
+
+URI: auth.html.ko.euc-kr
+Content-Language: ko
+Content-type: text/html; charset=EUC-KR
+
+URI: auth.html.tr.utf8
+Content-Language: tr
+Content-type: text/html; charset=UTF-8
diff --git a/docs/manual/howto/auth.html.en b/docs/manual/howto/auth.html.en
new file mode 100644
index 0000000..d8a9b0e
--- /dev/null
+++ b/docs/manual/howto/auth.html.en
@@ -0,0 +1,640 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head>
+<meta content="text/html; charset=UTF-8" http-equiv="Content-Type" />
+<!--
+ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+ This file is generated from xml source: DO NOT EDIT
+ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+ -->
+<title>Authentication and Authorization - Apache HTTP Server Version 2.4</title>
+<link href="../style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" />
+<link href="../style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" />
+<link href="../style/css/manual-print.css" rel="stylesheet" media="print" type="text/css" /><link rel="stylesheet" type="text/css" href="../style/css/prettify.css" />
+<script src="../style/scripts/prettify.min.js" type="text/javascript">
+</script>
+
+<link href="../images/favicon.ico" rel="shortcut icon" /></head>
+<body id="manual-page"><div id="page-header">
+<p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a> | <a href="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p>
+<p class="apache">Apache HTTP Server Version 2.4</p>
+<img alt="" src="../images/feather.png" /></div>
+<div class="up"><a href="./"><img title="&lt;-" alt="&lt;-" src="../images/left.gif" /></a></div>
+<div id="path">
+<a href="http://www.apache.org/">Apache</a> &gt; <a href="http://httpd.apache.org/">HTTP Server</a> &gt; <a href="http://httpd.apache.org/docs/">Documentation</a> &gt; <a href="../">Version 2.4</a> &gt; <a href="./">How-To / Tutorials</a></div><div id="page-content"><div id="preamble"><h1>Authentication and Authorization</h1>
+<div class="toplang">
+<p><span>Available Languages: </span><a href="../en/howto/auth.html" title="English">&nbsp;en&nbsp;</a> |
+<a href="../es/howto/auth.html" hreflang="es" rel="alternate" title="Espa簽ol">&nbsp;es&nbsp;</a> |
+<a href="../fr/howto/auth.html" hreflang="fr" rel="alternate" title="Fran癟ais">&nbsp;fr&nbsp;</a> |
+<a href="../ja/howto/auth.html" hreflang="ja" rel="alternate" title="Japanese">&nbsp;ja&nbsp;</a> |
+<a href="../ko/howto/auth.html" hreflang="ko" rel="alternate" title="Korean">&nbsp;ko&nbsp;</a> |
+<a href="../tr/howto/auth.html" hreflang="tr" rel="alternate" title="T羹rk癟e">&nbsp;tr&nbsp;</a></p>
+</div>
+
+ <p>Authentication is any process by which you verify that
+ someone is who they claim they are. Authorization is any
+ process by which someone is allowed to be where they want to
+ go, or to have information that they want to have.</p>
+
+ <p>For general access control, see the <a href="access.html">Access
+ Control How-To</a>.</p>
+</div>
+<div id="quickview"><a href="https://www.apache.org/foundation/contributing.html" class="badge"><img src="https://www.apache.org/images/SupportApache-small.png" alt="Support Apache!" /></a><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#related">Related Modules and Directives</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#introduction">Introduction</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#theprerequisites">The Prerequisites</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#gettingitworking">Getting it working</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#lettingmorethanonepersonin">Letting more than one
+person in</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#possibleproblems">Possible problems</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#dbmdbd">Alternate password storage</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#multprovider">Using multiple providers</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#beyond">Beyond just authorization</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#socache">Authentication Caching</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#moreinformation">More information</a></li>
+</ul><h3>See also</h3><ul class="seealso"><li><a href="#comments_section">Comments</a></li></ul></div>
+<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="related" id="related">Related Modules and Directives</a></h2>
+
+<p>There are three types of modules involved in the authentication and
+authorization process. You will usually need to choose at least one
+module from each group.</p>
+
+<ul>
+ <li>Authentication type (see the
+ <code class="directive"><a href="../mod/mod_authn_core.html#authtype">AuthType</a></code> directive)
+ <ul>
+ <li><code class="module"><a href="../mod/mod_auth_basic.html">mod_auth_basic</a></code></li>
+ <li><code class="module"><a href="../mod/mod_auth_digest.html">mod_auth_digest</a></code></li>
+ </ul>
+ </li>
+ <li>Authentication provider (see the
+ <code class="directive"><a href="../mod/mod_auth_basic.html#authbasicprovider">AuthBasicProvider</a></code> and
+ <code class="directive"><a href="../mod/mod_auth_digest.html#authdigestprovider">AuthDigestProvider</a></code> directives)
+
+ <ul>
+ <li><code class="module"><a href="../mod/mod_authn_anon.html">mod_authn_anon</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authn_dbd.html">mod_authn_dbd</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authn_dbm.html">mod_authn_dbm</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authn_file.html">mod_authn_file</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authnz_ldap.html">mod_authnz_ldap</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authn_socache.html">mod_authn_socache</a></code></li>
+ </ul>
+ </li>
+ <li>Authorization (see the
+ <code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code> directive)
+ <ul>
+ <li><code class="module"><a href="../mod/mod_authnz_ldap.html">mod_authnz_ldap</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authz_dbd.html">mod_authz_dbd</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authz_dbm.html">mod_authz_dbm</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authz_groupfile.html">mod_authz_groupfile</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authz_host.html">mod_authz_host</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authz_owner.html">mod_authz_owner</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authz_user.html">mod_authz_user</a></code></li>
+ </ul>
+ </li>
+</ul>
+
+ <p>In addition to these modules, there are also
+ <code class="module"><a href="../mod/mod_authn_core.html">mod_authn_core</a></code> and
+ <code class="module"><a href="../mod/mod_authz_core.html">mod_authz_core</a></code>. These modules implement core
+ directives that are core to all auth modules.</p>
+
+ <p>The module <code class="module"><a href="../mod/mod_authnz_ldap.html">mod_authnz_ldap</a></code> is both an
+ authentication and authorization provider. The module
+ <code class="module"><a href="../mod/mod_authz_host.html">mod_authz_host</a></code> provides authorization
+ and access control based on hostname, IP address or characteristics
+ of the request, but is not part of the authentication provider
+ system. For backwards compatibility with the mod_access, there is
+ a new module <code class="module"><a href="../mod/mod_access_compat.html">mod_access_compat</a></code>.</p>
+
+ <p>You probably also want to take a look at the <a href="access.html">Access Control</a> howto, which discusses the
+ various ways to control access to your server.</p>
+
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="introduction" id="introduction">Introduction</a></h2>
+ <p>If you have information on your web site that is sensitive
+ or intended for only a small group of people, the techniques in
+ this article will help you make sure that the people that see
+ those pages are the people that you wanted to see them.</p>
+
+ <p>This article covers the "standard" way of protecting parts
+ of your web site that most of you are going to use.</p>
+
+ <div class="note"><h3>Note:</h3>
+ <p>If your data really needs to be secure, consider using
+ <code class="module"><a href="../mod/mod_ssl.html">mod_ssl</a></code> in addition to any authentication.</p>
+ </div>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="theprerequisites" id="theprerequisites">The Prerequisites</a></h2>
+ <p>The directives discussed in this article will need to go
+ either in your main server configuration file (typically in a
+ <code class="directive"><a href="../mod/core.html#directory">&lt;Directory&gt;</a></code> section), or
+ in per-directory configuration files (<code>.htaccess</code> files).</p>
+
+ <p>If you plan to use <code>.htaccess</code> files, you will
+ need to have a server configuration that permits putting
+ authentication directives in these files. This is done with the
+ <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code> directive, which
+ specifies which directives, if any, may be put in per-directory
+ configuration files.</p>
+
+ <p>Since we're talking here about authentication, you will need
+ an <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code> directive like the
+ following:</p>
+
+ <pre class="prettyprint lang-config">AllowOverride AuthConfig</pre>
+
+
+ <p>Or, if you are just going to put the directives directly in
+ your main server configuration file, you will of course need to
+ have write permission to that file.</p>
+
+ <p>And you'll need to know a little bit about the directory
+ structure of your server, in order to know where some files are
+ kept. This should not be terribly difficult, and I'll try to
+ make this clear when we come to that point.</p>
+
+ <p>You will also need to make sure that the modules
+ <code class="module"><a href="../mod/mod_authn_core.html">mod_authn_core</a></code> and <code class="module"><a href="../mod/mod_authz_core.html">mod_authz_core</a></code>
+ have either been built into the httpd binary or loaded by the
+ httpd.conf configuration file. Both of these modules provide core
+ directives and functionality that are critical to the configuration
+ and use of authentication and authorization in the web server.</p>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="gettingitworking" id="gettingitworking">Getting it working</a></h2>
+ <p>Here's the basics of password protecting a directory on your
+ server.</p>
+
+ <p>First, you need to create a password file. Exactly how you do
+ this will vary depending on what authentication provider you have
+ chosen. More on that later. To start with, we'll use a text password
+ file.</p>
+
+ <p>This file should be
+ placed somewhere not accessible from the web. This is so that
+ folks cannot download the password file. For example, if your
+ documents are served out of <code>/usr/local/apache/htdocs</code>, you
+ might want to put the password file(s) in
+ <code>/usr/local/apache/passwd</code>.</p>
+
+ <p>To create the file, use the <code class="program"><a href="../programs/htpasswd.html">htpasswd</a></code> utility that
+ came with Apache. This will be located in the <code>bin</code> directory
+ of wherever you installed Apache. If you have installed Apache from
+ a third-party package, it may be in your execution path.</p>
+
+ <p>To create the file, type:</p>
+
+ <div class="example"><p><code>
+ htpasswd -c /usr/local/apache/passwd/passwords rbowen
+ </code></p></div>
+
+ <p><code class="program"><a href="../programs/htpasswd.html">htpasswd</a></code> will ask you for the password, and
+ then ask you to type it again to confirm it:</p>
+
+ <div class="example"><p><code>
+ # htpasswd -c /usr/local/apache/passwd/passwords rbowen<br />
+ New password: mypassword<br />
+ Re-type new password: mypassword<br />
+ Adding password for user rbowen
+ </code></p></div>
+
+ <p>If <code class="program"><a href="../programs/htpasswd.html">htpasswd</a></code> is not in your path, of course
+ you'll have to type the full path to the file to get it to run.
+ With a default installation, it's located at
+ <code>/usr/local/apache2/bin/htpasswd</code></p>
+
+ <p>Next, you'll need to configure the server to request a
+ password and tell the server which users are allowed access.
+ You can do this either by editing the <code>httpd.conf</code>
+ file or using an <code>.htaccess</code> file. For example, if
+ you wish to protect the directory
+ <code>/usr/local/apache/htdocs/secret</code>, you can use the
+ following directives, either placed in the file
+ <code>/usr/local/apache/htdocs/secret/.htaccess</code>, or
+ placed in <code>httpd.conf</code> inside a &lt;Directory
+ "/usr/local/apache/htdocs/secret"&gt; section.</p>
+
+ <pre class="prettyprint lang-config">AuthType Basic
+AuthName "Restricted Files"
+# (Following line optional)
+AuthBasicProvider file
+AuthUserFile "/usr/local/apache/passwd/passwords"
+Require user rbowen</pre>
+
+
+ <p>Let's examine each of those directives individually. The <code class="directive"><a href="../mod/mod_authn_core.html#authtype">AuthType</a></code> directive selects
+ the method that is used to authenticate the user. The most
+ common method is <code>Basic</code>, and this is the method
+ implemented by <code class="module"><a href="../mod/mod_auth_basic.html">mod_auth_basic</a></code>. It is important to be aware,
+ however, that Basic authentication sends the password from the client to
+ the server unencrypted. This method should therefore not be used for
+ highly sensitive data, unless accompanied by <code class="module"><a href="../mod/mod_ssl.html">mod_ssl</a></code>.
+ Apache supports one other authentication method:
+ <code>AuthType Digest</code>. This method is implemented by <code class="module"><a href="../mod/mod_auth_digest.html">mod_auth_digest</a></code> and was intended to be more secure. This is no
+ longer the case and the connection should be encrypted with <code class="module"><a href="../mod/mod_ssl.html">mod_ssl</a></code> instead.</p>
+
+ <p>The <code class="directive"><a href="../mod/mod_authn_core.html#authname">AuthName</a></code> directive sets
+ the <dfn>Realm</dfn> to be used in the authentication. The realm serves
+ two major functions. First, the client often presents this information to
+ the user as part of the password dialog box. Second, it is used by the
+ client to determine what password to send for a given authenticated
+ area.</p>
+
+ <p>So, for example, once a client has authenticated in the
+ <code>"Restricted Files"</code> area, it will automatically
+ retry the same password for any area on the same server that is
+ marked with the <code>"Restricted Files"</code> Realm.
+ Therefore, you can prevent a user from being prompted more than
+ once for a password by letting multiple restricted areas share
+ the same realm. Of course, for security reasons, the client
+ will always need to ask again for the password whenever the
+ hostname of the server changes.</p>
+
+ <p>The <code class="directive"><a href="../mod/mod_auth_basic.html#authbasicprovider">AuthBasicProvider</a></code> is,
+ in this case, optional, since <code>file</code> is the default value
+ for this directive. You'll need to use this directive if you are
+ choosing a different source for authentication, such as
+ <code class="module"><a href="../mod/mod_authn_dbm.html">mod_authn_dbm</a></code> or <code class="module"><a href="../mod/mod_authn_dbd.html">mod_authn_dbd</a></code>.</p>
+
+ <p>The <code class="directive"><a href="../mod/mod_authn_file.html#authuserfile">AuthUserFile</a></code>
+ directive sets the path to the password file that we just
+ created with <code class="program"><a href="../programs/htpasswd.html">htpasswd</a></code>. If you have a large number
+ of users, it can be quite slow to search through a plain text
+ file to authenticate the user on each request. Apache also has
+ the ability to store user information in fast database files.
+ The <code class="module"><a href="../mod/mod_authn_dbm.html">mod_authn_dbm</a></code> module provides the <code class="directive"><a href="../mod/mod_authn_dbm.html#authdbmuserfile">AuthDBMUserFile</a></code> directive. These
+ files can be created and manipulated with the <code class="program"><a href="../programs/dbmmanage.html">dbmmanage</a></code> and <code class="program"><a href="../programs/htdbm.html">htdbm</a></code> programs. Many
+ other types of authentication options are available from third
+ party modules.</p>
+
+ <p>Finally, the <code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code>
+ directive provides the authorization part of the process by
+ setting the user that is allowed to access this region of the
+ server. In the next section, we discuss various ways to use the
+ <code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code> directive.</p>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="lettingmorethanonepersonin" id="lettingmorethanonepersonin">Letting more than one
+person in</a></h2>
+ <p>The directives above only let one person (specifically
+ someone with a username of <code>rbowen</code>) into the
+ directory. In most cases, you'll want to let more than one
+ person in. This is where the <code class="directive"><a href="../mod/mod_authz_groupfile.html#authgroupfile">AuthGroupFile</a></code> comes in.</p>
+
+ <p>If you want to let more than one person in, you'll need to
+ create a group file that associates group names with a list of
+ users in that group. The format of this file is pretty simple,
+ and you can create it with your favorite editor. The contents
+ of the file will look like this:</p>
+
+ <div class="example"><p><code>
+ GroupName: rbowen dpitts sungo rshersey
+ </code></p></div>
+
+ <p>That's just a list of the members of the group in a long
+ line separated by spaces.</p>
+
+ <p>To add a user to your already existing password file,
+ type:</p>
+
+ <div class="example"><p><code>
+ htpasswd /usr/local/apache/passwd/passwords dpitts
+ </code></p></div>
+
+ <p>You'll get the same response as before, but it will be
+ appended to the existing file, rather than creating a new file.
+ (It's the <code>-c</code> that makes it create a new password
+ file).</p>
+
+ <p>Now, you need to modify your <code>.htaccess</code> file or
+ <code class="directive"><a href="../mod/core.html#directory">&lt;Directory&gt;</a></code> block
+ to look like the following:</p>
+
+ <pre class="prettyprint lang-config">AuthType Basic
+AuthName "By Invitation Only"
+# Optional line:
+AuthBasicProvider file
+AuthUserFile "/usr/local/apache/passwd/passwords"
+AuthGroupFile "/usr/local/apache/passwd/groups"
+Require group GroupName</pre>
+
+
+ <p>Now, anyone that is listed in the group <code>GroupName</code>,
+ and has an entry in the <code>password</code> file, will be let in, if
+ they type the correct password.</p>
+
+ <p>There's another way to let multiple users in that is less
+ specific. Rather than creating a group file, you can just use
+ the following directive:</p>
+
+ <pre class="prettyprint lang-config">Require valid-user</pre>
+
+
+ <p>Using that rather than the <code>Require user rbowen</code>
+ line will allow anyone in that is listed in the password file,
+ and who correctly enters their password.</p>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="possibleproblems" id="possibleproblems">Possible problems</a></h2>
+ <p>Because of the way that Basic authentication is specified,
+ your username and password must be verified every time you
+ request a document from the server. This is even if you're
+ reloading the same page, and for every image on the page (if
+ they come from a protected directory). As you can imagine, this
+ slows things down a little. The amount that it slows things
+ down is proportional to the size of the password file, because
+ it has to open up that file, and go down the list of users
+ until it gets to your name. And it has to do this every time a
+ page is loaded.</p>
+
+ <p>A consequence of this is that there's a practical limit to
+ how many users you can put in one password file. This limit
+ will vary depending on the performance of your particular
+ server machine, but you can expect to see slowdowns once you
+ get above a few hundred entries, and may wish to consider a
+ different authentication method at that time.</p>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="dbmdbd" id="dbmdbd">Alternate password storage</a></h2>
+
+ <p>Because storing passwords in plain text files has the above
+ problems, you may wish to store your passwords somewhere else, such
+ as in a database.</p>
+
+ <p><code class="module"><a href="../mod/mod_authn_dbm.html">mod_authn_dbm</a></code> and <code class="module"><a href="../mod/mod_authn_dbd.html">mod_authn_dbd</a></code> are two
+ modules which make this possible. Rather than selecting <code><code class="directive"><a href="../mod/mod_auth_basic.html#authbasicprovider">AuthBasicProvider</a></code> file</code>, instead
+ you can choose <code>dbm</code> or <code>dbd</code> as your storage
+ format.</p>
+
+ <p>To select a dbm file rather than a text file, for example:</p>
+
+ <pre class="prettyprint lang-config">&lt;Directory "/www/docs/private"&gt;
+ AuthName "Private"
+ AuthType Basic
+ AuthBasicProvider dbm
+ AuthDBMUserFile "/www/passwords/passwd.dbm"
+ Require valid-user
+&lt;/Directory&gt;</pre>
+
+
+ <p>Other options are available. Consult the
+ <code class="module"><a href="../mod/mod_authn_dbm.html">mod_authn_dbm</a></code> documentation for more details.</p>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="multprovider" id="multprovider">Using multiple providers</a></h2>
+
+ <p>With the introduction of the new provider based authentication and
+ authorization architecture, you are no longer locked into a single
+ authentication or authorization method. In fact any number of the
+ providers can be mixed and matched to provide you with exactly the
+ scheme that meets your needs. In the following example, both the
+ file and LDAP based authentication providers are being used.</p>
+
+ <pre class="prettyprint lang-config">&lt;Directory "/www/docs/private"&gt;
+ AuthName "Private"
+ AuthType Basic
+ AuthBasicProvider file ldap
+ AuthUserFile "/usr/local/apache/passwd/passwords"
+ AuthLDAPURL ldap://ldaphost/o=yourorg
+ Require valid-user
+&lt;/Directory&gt;</pre>
+
+
+ <p>In this example the file provider will attempt to authenticate
+ the user first. If it is unable to authenticate the user, the LDAP
+ provider will be called. This allows the scope of authentication
+ to be broadened if your organization implements more than
+ one type of authentication store. Other authentication and authorization
+ scenarios may include mixing one type of authentication with a
+ different type of authorization. For example, authenticating against
+ a password file yet authorizing against an LDAP directory.</p>
+
+ <p>Just as multiple authentication providers can be implemented, multiple
+ authorization methods can also be used. In this example both file group
+ authorization as well as LDAP group authorization is being used.</p>
+
+ <pre class="prettyprint lang-config">&lt;Directory "/www/docs/private"&gt;
+ AuthName "Private"
+ AuthType Basic
+ AuthBasicProvider file
+ AuthUserFile "/usr/local/apache/passwd/passwords"
+ AuthLDAPURL ldap://ldaphost/o=yourorg
+ AuthGroupFile "/usr/local/apache/passwd/groups"
+ Require group GroupName
+ Require ldap-group cn=mygroup,o=yourorg
+&lt;/Directory&gt;</pre>
+
+
+ <p>To take authorization a little further, authorization container
+ directives such as
+ <code class="directive"><a href="../mod/mod_authz_core.html#requireall">&lt;RequireAll&gt;</a></code>
+ and
+ <code class="directive"><a href="../mod/mod_authz_core.html#requireany">&lt;RequireAny&gt;</a></code>
+ allow logic to be applied so that the order in which authorization
+ is handled can be completely controlled through the configuration.
+ See <a href="../mod/mod_authz_core.html#logic">Authorization
+ Containers</a> for an example of how they may be applied.</p>
+
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="beyond" id="beyond">Beyond just authorization</a></h2>
+
+ <p>The way that authorization can be applied is now much more flexible
+ than just a single check against a single data store. Ordering, logic
+ and choosing how authorization will be done is now possible.</p>
+
+ <h3><a name="authandororder" id="authandororder">Applying logic and ordering</a></h3>
+ <p>Controlling how and in what order authorization will be applied
+ has been a bit of a mystery in the past. In Apache 2.2 a provider-based
+ authentication mechanism was introduced to decouple the actual
+ authentication process from authorization and supporting functionality.
+ One of the side benefits was that authentication providers could be
+ configured and called in a specific order which didn't depend on the
+ load order of the auth module itself. This same provider based mechanism
+ has been brought forward into authorization as well. What this means is
+ that the <code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code> directive
+ not only specifies which authorization methods should be used, it also
+ specifies the order in which they are called. Multiple authorization
+ methods are called in the same order in which the
+ <code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code> directives
+ appear in the configuration.</p>
+
+ <p>With the introduction of authorization container directives
+ such as
+ <code class="directive"><a href="../mod/mod_authz_core.html#requireall">&lt;RequireAll&gt;</a></code>
+ and
+ <code class="directive"><a href="../mod/mod_authz_core.html#requireany">&lt;RequireAny&gt;</a></code>,
+ the configuration also has control over when the
+ authorization methods are called and what criteria determines when
+ access is granted. See
+ <a href="../mod/mod_authz_core.html#logic">Authorization Containers</a>
+ for an example of how they may be used to express complex
+ authorization logic.</p>
+
+ <p>By default all
+ <code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code>
+ directives are handled as though contained within a
+ <code class="directive"><a href="../mod/mod_authz_core.html#requireany">&lt;RequireAny&gt;</a></code>
+ container directive. In other words, if
+ any of the specified authorization methods succeed, then authorization
+ is granted.</p>
+
+
+
+ <h3><a name="reqaccessctrl" id="reqaccessctrl">Using authorization providers for access control</a></h3>
+ <p>Authentication by username and password is only part of the
+ story. Frequently you want to let people in based on something
+ other than who they are. Something such as where they are
+ coming from.</p>
+
+ <p>The authorization providers <code>all</code>,
+ <code>env</code>, <code>host</code> and <code>ip</code> let you
+ allow or deny access based on other host based criteria such as
+ host name or ip address of the machine requesting a
+ document.</p>
+
+ <p>The usage of these providers is specified through the
+ <code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code> directive.
+ This directive registers the authorization providers
+ that will be called during the authorization stage of the request
+ processing. For example:</p>
+
+ <pre class="prettyprint lang-config">Require ip <var>address</var>
+ </pre>
+
+
+ <p>where <var>address</var> is an IP address (or a partial IP
+ address) or:</p>
+
+ <pre class="prettyprint lang-config">Require host <var>domain_name</var>
+ </pre>
+
+
+ <p>where <var>domain_name</var> is a fully qualified domain name
+ (or a partial domain name); you may provide multiple addresses or
+ domain names, if desired.</p>
+
+ <p>For example, if you have someone spamming your message
+ board, and you want to keep them out, you could do the
+ following:</p>
+
+ <pre class="prettyprint lang-config">&lt;RequireAll&gt;
+ Require all granted
+ Require not ip 10.252.46.165
+&lt;/RequireAll&gt;</pre>
+
+
+ <p>Visitors coming from that address will not be able to see
+ the content covered by this directive. If, instead, you have a
+ machine name, rather than an IP address, you can use that.</p>
+
+ <pre class="prettyprint lang-config">&lt;RequireAll&gt;
+ Require all granted
+ Require not host host.example.com
+&lt;/RequireAll&gt;</pre>
+
+
+ <p>And, if you'd like to block access from an entire domain,
+ you can specify just part of an address or domain name:</p>
+
+ <pre class="prettyprint lang-config">&lt;RequireAll&gt;
+ Require all granted
+ Require not ip 192.168.205
+ Require not host phishers.example.com moreidiots.example
+ Require not host ke
+&lt;/RequireAll&gt;</pre>
+
+
+ <p>Using <code class="directive"><a href="../mod/mod_authz_core.html#requireall">&lt;RequireAll&gt;</a></code>
+ with multiple <code class="directive"><a href="../mod/mod_authz_core.html#require">&lt;Require&gt;</a></code> directives, each negated with <code>not</code>,
+ will only allow access, if all of negated conditions are true. In other words,
+ access will be blocked, if any of the negated conditions fails.</p>
+
+
+
+ <h3><a name="filesystem" id="filesystem">Access Control backwards compatibility</a></h3>
+ <p>One of the side effects of adopting a provider based mechanism for
+ authentication is that the previous access control directives
+ <code class="directive"><a href="../mod/mod_access_compat.html#order">Order</a></code>,
+ <code class="directive"><a href="../mod/mod_access_compat.html#allow">Allow</a></code>,
+ <code class="directive"><a href="../mod/mod_access_compat.html#deny">Deny</a></code> and
+ <code class="directive"><a href="../mod/mod_access_compat.html#satisfy">Satisfy</a></code> are no longer needed.
+ However to provide backwards compatibility for older configurations, these
+ directives have been moved to the <code class="module"><a href="../mod/mod_access_compat.html">mod_access_compat</a></code> module.</p>
+
+ <div class="warning"><h3>Note</h3>
+ <p>The directives provided by <code class="module"><a href="../mod/mod_access_compat.html">mod_access_compat</a></code> have
+ been deprecated by <code class="module"><a href="../mod/mod_authz_host.html">mod_authz_host</a></code>.
+ Mixing old directives like <code class="directive"><a href="../mod/mod_access_compat.html#order">Order</a></code>, <code class="directive"><a href="../mod/mod_access_compat.html#allow">Allow</a></code> or <code class="directive"><a href="../mod/mod_access_compat.html#deny">Deny</a></code> with new ones like
+ <code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code> is technically possible
+ but discouraged. The <code class="module"><a href="../mod/mod_access_compat.html">mod_access_compat</a></code> module was created to support
+ configurations containing only old directives to facilitate the 2.4 upgrade.
+ Please check the <a href="../upgrading.html">upgrading</a> guide for more
+ information.
+ </p>
+ </div>
+
+
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="socache" id="socache">Authentication Caching</a></h2>
+ <p>There may be times when authentication puts an unacceptable load
+ on a provider or on your network. This is most likely to affect users
+ of <code class="module"><a href="../mod/mod_authn_dbd.html">mod_authn_dbd</a></code> (or third-party/custom providers).
+ To deal with this, HTTPD 2.3/2.4 introduces a new caching provider
+ <code class="module"><a href="../mod/mod_authn_socache.html">mod_authn_socache</a></code> to cache credentials and reduce
+ the load on the origin provider(s).</p>
+ <p>This may offer a substantial performance boost to some users.</p>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="moreinformation" id="moreinformation">More information</a></h2>
+ <p>You should also read the documentation for
+ <code class="module"><a href="../mod/mod_auth_basic.html">mod_auth_basic</a></code> and <code class="module"><a href="../mod/mod_authz_host.html">mod_authz_host</a></code>
+ which contain some more information about how this all works. The
+ directive <code class="directive"><a href="../mod/mod_authn_core.html#authnprovideralias">&lt;AuthnProviderAlias&gt;</a></code> can also help
+ in simplifying certain authentication configurations.</p>
+
+ <p>The various ciphers supported by Apache for authentication data are
+ explained in <a href="../misc/password_encryptions.html">Password
+ Encryptions</a>.</p>
+
+ <p>And you may want to look at the <a href="access.html">Access
+ Control</a> howto, which discusses a number of related topics.</p>
+
+</div></div>
+<div class="bottomlang">
+<p><span>Available Languages: </span><a href="../en/howto/auth.html" title="English">&nbsp;en&nbsp;</a> |
+<a href="../es/howto/auth.html" hreflang="es" rel="alternate" title="Espa簽ol">&nbsp;es&nbsp;</a> |
+<a href="../fr/howto/auth.html" hreflang="fr" rel="alternate" title="Fran癟ais">&nbsp;fr&nbsp;</a> |
+<a href="../ja/howto/auth.html" hreflang="ja" rel="alternate" title="Japanese">&nbsp;ja&nbsp;</a> |
+<a href="../ko/howto/auth.html" hreflang="ko" rel="alternate" title="Korean">&nbsp;ko&nbsp;</a> |
+<a href="../tr/howto/auth.html" hreflang="tr" rel="alternate" title="T羹rk癟e">&nbsp;tr&nbsp;</a></p>
+</div><div class="top"><a href="#page-header"><img src="../images/up.gif" alt="top" /></a></div><div class="section"><h2><a id="comments_section" name="comments_section">Comments</a></h2><div class="warning"><strong>Notice:</strong><br />This is not a Q&amp;A section. Comments placed here should be pointed towards suggestions on improving the documentation or server, and may be removed by our moderators if they are either implemented or considered invalid/off-topic. Questions on how to manage the Apache HTTP Server should be directed at either our IRC channel, #httpd, on Libera.chat, or sent to our <a href="https://httpd.apache.org/lists.html">mailing lists</a>.</div>
+<script type="text/javascript"><!--//--><![CDATA[//><!--
+var comments_shortname = 'httpd';
+var comments_identifier = 'http://httpd.apache.org/docs/2.4/howto/auth.html';
+(function(w, d) {
+ if (w.location.hostname.toLowerCase() == "httpd.apache.org") {
+ d.write('<div id="comments_thread"><\/div>');
+ var s = d.createElement('script');
+ s.type = 'text/javascript';
+ s.async = true;
+ s.src = 'https://comments.apache.org/show_comments.lua?site=' + comments_shortname + '&page=' + comments_identifier;
+ (d.getElementsByTagName('head')[0] || d.getElementsByTagName('body')[0]).appendChild(s);
+ }
+ else {
+ d.write('<div id="comments_thread">Comments are disabled for this page at the moment.<\/div>');
+ }
+})(window, document);
+//--><!]]></script></div><div id="footer">
+<p class="apache">Copyright 2023 The Apache Software Foundation.<br />Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p>
+<p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a> | <a href="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p></div><script type="text/javascript"><!--//--><![CDATA[//><!--
+if (typeof(prettyPrint) !== 'undefined') {
+ prettyPrint();
+}
+//--><!]]></script>
+</body></html> \ No newline at end of file
diff --git a/docs/manual/howto/auth.html.es b/docs/manual/howto/auth.html.es
new file mode 100644
index 0000000..fd72860
--- /dev/null
+++ b/docs/manual/howto/auth.html.es
@@ -0,0 +1,717 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="es" xml:lang="es"><head>
+<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type" />
+<!--
+ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+ This file is generated from xml source: DO NOT EDIT
+ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+ -->
+<title>Autenticaci&#243;n y Autorizaci&#243;n - Servidor HTTP Apache Versi&#243;n 2.4</title>
+<link href="../style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" />
+<link href="../style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" />
+<link href="../style/css/manual-print.css" rel="stylesheet" media="print" type="text/css" /><link rel="stylesheet" type="text/css" href="../style/css/prettify.css" />
+<script src="../style/scripts/prettify.min.js" type="text/javascript">
+</script>
+
+<link href="../images/favicon.ico" rel="shortcut icon" /></head>
+<body id="manual-page"><div id="page-header">
+<p class="menu"><a href="../mod/">M&#243;dulos</a> | <a href="../mod/directives.html">Directivas</a> | <a href="http://wiki.apache.org/httpd/FAQ">Preguntas Frecuentes</a> | <a href="../glossary.html">Glosario</a> | <a href="../sitemap.html">Mapa del sitio web</a></p>
+<p class="apache">Versi&#243;n 2.4 del Servidor HTTP Apache</p>
+<img alt="" src="../images/feather.png" /></div>
+<div class="up"><a href="./"><img title="&lt;-" alt="&lt;-" src="../images/left.gif" /></a></div>
+<div id="path">
+<a href="http://www.apache.org/">Apache</a> &gt; <a href="http://httpd.apache.org/">Servidor HTTP</a> &gt; <a href="http://httpd.apache.org/docs/">Documentaci&#243;n</a> &gt; <a href="../">Versi&#243;n 2.4</a> &gt; <a href="./">How-To / Tutoriales</a></div><div id="page-content"><div id="preamble"><h1>Autenticaci&#243;n y Autorizaci&#243;n</h1>
+<div class="toplang">
+<p><span>Idiomas disponibles: </span><a href="../en/howto/auth.html" hreflang="en" rel="alternate" title="English">&nbsp;en&nbsp;</a> |
+<a href="../es/howto/auth.html" title="Espa&#241;ol">&nbsp;es&nbsp;</a> |
+<a href="../fr/howto/auth.html" hreflang="fr" rel="alternate" title="Fran&#231;ais">&nbsp;fr&nbsp;</a> |
+<a href="../ja/howto/auth.html" hreflang="ja" rel="alternate" title="Japanese">&nbsp;ja&nbsp;</a> |
+<a href="../ko/howto/auth.html" hreflang="ko" rel="alternate" title="Korean">&nbsp;ko&nbsp;</a> |
+<a href="../tr/howto/auth.html" hreflang="tr" rel="alternate" title="T&#252;rk&#231;e">&nbsp;tr&nbsp;</a></p>
+</div>
+<div class="outofdate">Esta traducci&#243;n podr&#237;a estar
+ obsoleta. Consulte la versi&#243;n en ingl&#233;s de la
+ documentaci&#243;n para comprobar si se han producido cambios
+ recientemente.</div>
+
+ <p>Autenticaci&#243;n es cualquier proceso por el cu&#225;l se verifica que uno es
+ quien dice ser. Autorizaci&#243;n es cualquier proceso en el cu&#225;l cualquiera
+ est&#225; permitido a estar donde se quiera, o tener informaci&#243;n la cu&#225;l se
+ quiera tener.
+ </p>
+
+ <p>Para informaci&#243;n de control de acceso de forma gen&#233;rica visite<a href="access.html">How to de Control de Acceso</a>.</p>
+</div>
+<div id="quickview"><a href="https://www.apache.org/foundation/contributing.html" class="badge"><img src="https://www.apache.org/images/SupportApache-small.png" alt="Support Apache!" /></a><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#related">M&#243;dulos y Directivas Relacionados</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#introduction">Introducci&#243;n</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#theprerequisites">Los Prerequisitos</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#gettingitworking">Conseguir que funcione</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#lettingmorethanonepersonin">Dejar que m&#225;s de una persona
+ entre</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#possibleproblems">Posibles Problemas</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#dbmdbd">M&#233;todo alternativo de almacenamiento de las
+ contrase&#241;as</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#multprovider">Uso de m&#250;ltiples proveedores</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#beyond">M&#225;s all&#225; de la Autorizaci&#243;n</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#socache">Cache de Autenticaci&#243;n</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#moreinformation">M&#225;s informaci&#243;n</a></li>
+</ul><h3>Consulte tambi&#233;n</h3><ul class="seealso"><li><a href="#comments_section">Comentarios</a></li></ul></div>
+<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="related" id="related">M&#243;dulos y Directivas Relacionados</a></h2>
+
+<p>Hay tres tipos de m&#243;dulos involucrados en los procesos de la autenticaci&#243;n
+ y autorizaci&#243;n. Normalmente deber&#225;s escoger al menos un m&#243;dulo de cada grupo.</p>
+
+<ul>
+ <li>Modos de Autenticaci&#243;n (consulte la directiva
+ <code class="directive"><a href="../mod/mod_authn_core.html#authtype">AuthType</a></code> )
+ <ul>
+ <li><code class="module"><a href="../mod/mod_auth_basic.html">mod_auth_basic</a></code></li>
+ <li><code class="module"><a href="../mod/mod_auth_digest.html">mod_auth_digest</a></code></li>
+ </ul>
+ </li>
+ <li>Proveedor de Autenticaci&#243;n (consulte la directiva
+ <code class="directive"><a href="../mod/mod_auth_basic.html#authbasicprovider">AuthBasicProvider</a></code> y
+ <code class="directive"><a href="../mod/mod_auth_digest.html#authdigestprovider">AuthDigestProvider</a></code>)
+
+ <ul>
+ <li><code class="module"><a href="../mod/mod_authn_anon.html">mod_authn_anon</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authn_dbd.html">mod_authn_dbd</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authn_dbm.html">mod_authn_dbm</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authn_file.html">mod_authn_file</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authnz_ldap.html">mod_authnz_ldap</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authn_socache.html">mod_authn_socache</a></code></li>
+ </ul>
+ </li>
+ <li>Autorizaci&#243;n (consulte la directiva
+ <code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code>)
+ <ul>
+ <li><code class="module"><a href="../mod/mod_authnz_ldap.html">mod_authnz_ldap</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authz_dbd.html">mod_authz_dbd</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authz_dbm.html">mod_authz_dbm</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authz_groupfile.html">mod_authz_groupfile</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authz_host.html">mod_authz_host</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authz_owner.html">mod_authz_owner</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authz_user.html">mod_authz_user</a></code></li>
+ </ul>
+ </li>
+</ul>
+
+ <p>A parte de &#233;stos m&#243;dulos, tambi&#233;n est&#225;n
+ <code class="module"><a href="../mod/mod_authn_core.html">mod_authn_core</a></code> y
+ <code class="module"><a href="../mod/mod_authz_core.html">mod_authz_core</a></code>. &#201;stos m&#243;dulos implementan las directivas
+ esenciales que son el centro de todos los m&#243;dulos de autenticaci&#243;n.</p>
+
+ <p>El m&#243;dulo <code class="module"><a href="../mod/mod_authnz_ldap.html">mod_authnz_ldap</a></code> es tanto un proveedor de
+ autenticaci&#243;n como de autorizaci&#243;n. El m&#243;dulo
+ <code class="module"><a href="../mod/mod_authz_host.html">mod_authz_host</a></code> proporciona autorizaci&#243;n y control de acceso
+ basado en el nombre del Host, la direcci&#243;n IP o caracter&#237;sticas de la propia
+ petici&#243;n, pero no es parte del sistema proveedor de
+ autenticaci&#243;n. Para tener compatibilidad inversa con el mod_access,
+ hay un nuevo modulo llamado <code class="module"><a href="../mod/mod_access_compat.html">mod_access_compat</a></code>.</p>
+
+ <p>Tambi&#233;n puedes mirar el how-to de <a href="access.html">Control de Acceso </a>, donde se plantean varias formas del control de acceso al servidor.</p>
+
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="introduction" id="introduction">Introducci&#243;n</a></h2>
+ <p>Si se tiene informaci&#243;n en nuestra p&#225;gina web que sea informaci&#243;n
+ sensible o pensada para un grupo reducido de usuarios/personas,
+ las t&#233;cnicas que se describen en este manual, le servir&#225;n
+ de ayuda para asegurarse de que las personas que ven esas p&#225;ginas sean
+ las personas que uno quiere.</p>
+
+ <p>Este art&#237;culo cubre la parte "est&#225;ndar" de c&#243;mo proteger partes de un
+ sitio web que muchos usar&#225;n.</p>
+
+ <div class="note"><h3>Nota:</h3>
+ <p>Si de verdad es necesario que tus datos est&#233;n en un sitio seguro,
+ considera usar <code class="module"><a href="../mod/mod_ssl.html">mod_ssl</a></code> como m&#233;todo de autenticaci&#243;n adicional a cualquier forma de autenticaci&#243;n.</p>
+ </div>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="theprerequisites" id="theprerequisites">Los Prerequisitos</a></h2>
+ <p>Las directivas que se usan en este art&#237;culo necesitaran ponerse ya sea
+ en el fichero de configuraci&#243;n principal del servidor ( t&#237;picamente en
+ la secci&#243;n
+ <code class="directive"><a href="../mod/core.html#directory">&lt;Directory&gt;</a></code> de httpd.conf ), o
+ en cada uno de los ficheros de configuraciones del propio directorio
+ (los archivos <code>.htaccess</code>).</p>
+
+ <p>Si planea usar los ficheros <code>.htaccess</code> , necesitar&#225;s
+ tener en la configuraci&#243;n global del servidor, una configuraci&#243;n que permita
+ poner directivas de autenticaci&#243;n en estos ficheros. Esto se hace con la
+ directiva <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code>, la cual especifica
+ que directivas, en su caso, pueden ser puestas en cada fichero de configuraci&#243;n
+ por directorio.</p>
+
+ <p>Ya que estamos hablando aqu&#237; de autenticaci&#243;n, necesitar&#225;s una directiva
+ <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code> como la siguiente:
+ </p>
+
+ <pre class="prettyprint lang-config">AllowOverride AuthConfig</pre>
+
+
+ <p>O, si solo se van a poner las directivas directamente en la configuraci&#243;n
+ principal del servidor, deber&#225;s tener, claro est&#225;, permisos de escritura
+ en el archivo. </p>
+
+ <p>Y necesitar&#225;s saber un poco de como est&#225; estructurado el &#225;rbol de
+ directorios de tu servidor, para poder saber donde se encuentran algunos
+ archivos. Esto no deber&#237;a ser una tarea dif&#237;cil, a&#250;n as&#237; intentaremos
+ dejarlo claro llegado el momento de comentar dicho aspecto.</p>
+
+ <p>Tambi&#233;n deber&#225;s de asegurarte de que los m&#243;dulos
+ <code class="module"><a href="../mod/mod_authn_core.html">mod_authn_core</a></code> y <code class="module"><a href="../mod/mod_authz_core.html">mod_authz_core</a></code>
+ han sido incorporados, o a&#241;adidos a la hora de compilar en tu binario httpd o
+ cargados mediante el archivo de configuraci&#243;n <code>httpd.conf</code>. Estos
+ dos m&#243;dulos proporcionan directivas b&#225;sicas y funcionalidades que son cr&#237;ticas
+ para la configuraci&#243;n y uso de autenticaci&#243;n y autorizaci&#243;n en el servidor web.</p>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="gettingitworking" id="gettingitworking">Conseguir que funcione</a></h2>
+ <p>Aqu&#237; est&#225; lo b&#225;sico de c&#243;mo proteger con contrase&#241;a un directorio en tu
+ servidor.</p>
+
+ <p>Primero, necesitar&#225;s crear un fichero de contrase&#241;a. Dependiendo de que
+ proveedor de autenticaci&#243;n se haya elegido, se har&#225; de una forma u otra. Para empezar,
+ usaremos un fichero de contrase&#241;a de tipo texto.</p>
+
+ <p>Este fichero deber&#225; estar en un sitio que no se pueda tener acceso desde
+ la web. Esto tambi&#233;n implica que nadie pueda descargarse el fichero de
+ contrase&#241;as. Por ejemplo, si tus documentos est&#225;n guardados fuera de
+ <code>/usr/local/apache/htdocs</code>, querr&#225;s poner tu archivo de contrase&#241;as en
+ <code>/usr/local/apache/passwd</code>.</p>
+
+ <p>Para crear el fichero de contrase&#241;as, usa la utilidad
+ <code class="program"><a href="../programs/htpasswd.html">htpasswd</a></code> que viene con Apache. Esta herramienta se
+ encuentra en el directorio <code>/bin</code> en donde sea que se ha
+ instalado el Apache. Si ha instalado Apache desde un paquete de terceros,
+ puede ser que se encuentre en su ruta de ejecuci&#243;n.</p>
+
+ <p>Para crear el fichero, escribiremos:</p>
+
+ <div class="example"><p><code>
+ htpasswd -c /usr/local/apache/passwd/passwords rbowen
+ </code></p></div>
+
+ <p><code class="program"><a href="../programs/htpasswd.html">htpasswd</a></code> te preguntar&#225; por una contrase&#241;a, y despu&#233;s
+ te pedir&#225; que la vuelvas a escribir para confirmarla:</p>
+
+ <div class="example"><p><code>
+ $ htpasswd -c /usr/local/apache/passwd/passwords rbowen<br />
+ New password: mypassword<br />
+ Re-type new password: mypassword<br />
+ Adding password for user rbowen
+ </code></p></div>
+
+ <p>Si <code class="program"><a href="../programs/htpasswd.html">htpasswd</a></code> no est&#225; en tu variable de entorno "path" del
+ sistema, por supuesto deber&#225;s escribir la ruta absoluta del ejecutable para
+ poder hacer que se ejecute. En una instalaci&#243;n por defecto, est&#225; en:
+ <code>/usr/local/apache2/bin/htpasswd</code></p>
+
+ <p>Lo pr&#243;ximo que necesitas, ser&#225; configurar el servidor para que pida una
+ contrase&#241;a y as&#237; decirle al servidor que usuarios est&#225;n autorizados a acceder.
+ Puedes hacer esto ya sea editando el fichero <code>httpd.conf</code>
+ de configuraci&#243;n o usando in fichero <code>.htaccess</code>. Por ejemplo,
+ si quieres proteger el directorio
+ <code>/usr/local/apache/htdocs/secret</code>, puedes usar las siguientes
+ directivas, ya sea en el fichero <code>.htaccess</code> localizado en
+ following directives, either placed in the file
+ <code>/usr/local/apache/htdocs/secret/.htaccess</code>, o
+ en la configuraci&#243;n global del servidor <code>httpd.conf</code> dentro de la
+ secci&#243;n &lt;Directory
+ "/usr/local/apache/htdocs/secret"&gt; , como se muestra a continuaci&#243;n:</p>
+
+ <pre class="prettyprint lang-config">&lt;Directory "/usr/local/apache/htdocs/secret"&gt;
+AuthType Basic
+AuthName "Restricted Files"
+# (Following line optional)
+AuthBasicProvider file
+AuthUserFile "/usr/local/apache/passwd/passwords"
+Require user rbowen
+&lt;/Directory&gt;</pre>
+
+
+ <p>Vamos a explicar cada una de las directivas individualmente.
+ La directiva <code class="directive"><a href="../mod/mod_authn_core.html#authtype">AuthType</a></code> selecciona el m&#233;todo
+ que se usa para autenticar al usuario. El m&#233;todo m&#225;s com&#250;n es
+ <code>Basic</code>, y &#233;ste es el m&#233;todo que implementa
+ <code class="module"><a href="../mod/mod_auth_basic.html">mod_auth_basic</a></code>. Es muy importante ser consciente,
+ de que la autenticaci&#243;n b&#225;sica, env&#237;a las contrase&#241;as desde el cliente
+ al servidor sin cifrar.
+ Este m&#233;todo por tanto, no debe ser utilizado para proteger datos muy sensibles,
+ a no ser que, este m&#233;todo de autenticaci&#243;n b&#225;sica, sea acompa&#241;ado del m&#243;dulo
+ <code class="module"><a href="../mod/mod_ssl.html">mod_ssl</a></code>.
+ Apache soporta otro m&#233;todo m&#225;s de autenticaci&#243;n que es del tipo
+ <code>AuthType Digest</code>. Este m&#233;todo, es implementado por el m&#243;dulo <code class="module"><a href="../mod/mod_auth_digest.html">mod_auth_digest</a></code> y con el se pretend&#237;a crear una autenticaci&#243;n m&#225;s
+ segura. Este ya no es el caso, ya que la conexi&#243;n deber&#225; realizarse con <code class="module"><a href="../mod/mod_ssl.html">mod_ssl</a></code> en su lugar.
+ </p>
+
+ <p>La directiva <code class="directive"><a href="../mod/mod_authn_core.html#authname">AuthName</a></code>
+ establece el <dfn>Realm</dfn> para ser usado en la autenticaci&#243;n. El
+ <dfn>Realm</dfn> tiene dos funciones principales.
+ La primera, el cliente presenta a menudo esta informaci&#243;n al usuario como
+ parte del cuadro de di&#225;logo de contrase&#241;a. La segunda, que es utilizado por
+ el cliente para determinar qu&#233; contrase&#241;a enviar a para una determinada zona
+ de autenticaci&#243;n.</p>
+
+ <p>As&#237; que, por ejemple, una vez que el cliente se ha autenticado en el &#225;rea de
+ los <code>"Ficheros Restringidos"</code>, entonces re-intentar&#225; autom&#225;ticamente
+ la misma contrase&#241;a para cualquier &#225;rea en el mismo servidor que es marcado
+ con el Realm de <code>"Ficheros Restringidos"</code>
+ Por lo tanto, puedes prevenir que a un usuario se le pida mas de una vez por su
+ contrase&#241;a, compartiendo as&#237; varias &#225;reas restringidas el mismo Realm
+ Por supuesto, por razones de seguridad, el cliente pedir&#225; siempre por una contrase&#241;a,
+ siempre y cuando el nombre del servidor cambie.
+ </p>
+
+ <p>La directiva <code class="directive"><a href="../mod/mod_auth_basic.html#authbasicprovider">AuthBasicProvider</a></code> es,
+ en este caso, opcional, ya que <code>file</code> es el valor por defecto
+ para esta directiva. Deber&#225;s usar esta directiva si estas usando otro medio
+ diferente para la autenticaci&#243;n, como por ejemplo
+ <code class="module"><a href="../mod/mod_authn_dbm.html">mod_authn_dbm</a></code> o <code class="module"><a href="../mod/mod_authn_dbd.html">mod_authn_dbd</a></code>.</p>
+
+ <p>La directiva <code class="directive"><a href="../mod/mod_authn_file.html#authuserfile">AuthUserFile</a></code>
+ establece el path al fichero de contrase&#241;as que acabamos de crear con el
+ comando <code class="program"><a href="../programs/htpasswd.html">htpasswd</a></code>. Si tiene un n&#250;mero muy grande de usuarios,
+ puede ser realmente lento el buscar el usuario en ese fichero de texto plano
+ para autenticar a los usuarios en cada petici&#243;n.
+ Apache tambi&#233;n tiene la habilidad de almacenar informaci&#243;n de usuarios en
+ unos ficheros de r&#225;pido acceso a modo de base de datos.
+ El m&#243;dulo <code class="module"><a href="../mod/mod_authn_dbm.html">mod_authn_dbm</a></code> proporciona la directiva <code class="directive"><a href="../mod/mod_authn_dbm.html#authdbmuserfile">AuthDBMUserFile</a></code>. Estos ficheros pueden ser creados y
+ manipulados con el programa <code class="program"><a href="../programs/dbmmanage.html">dbmmanage</a></code> y <code class="program"><a href="../programs/htdbm.html">htdbm</a></code>.
+ Muchos otros m&#233;todos de autenticaci&#243;n as&#237; como otras opciones, est&#225;n disponibles en
+ m&#243;dulos de terceros
+ <a href="http://modules.apache.org/">Base de datos de M&#243;dulos disponibles</a>.</p>
+
+ <p>Finalmente, la directiva <code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code>
+ proporciona la parte del proceso de autorizaci&#243;n estableciendo el o los
+ usuarios que se les est&#225; permitido acceder a una regi&#243;n del servidor.
+ En la pr&#243;xima secci&#243;n, discutiremos las diferentes v&#237;as de utilizar la
+ directiva <code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code>.</p>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="lettingmorethanonepersonin" id="lettingmorethanonepersonin">Dejar que m&#225;s de una persona
+ entre</a></h2>
+ <p>Las directivas mencionadas arriba s&#243;lo permiten a una persona
+ (especialmente con un usuario que en ej ejemplo es <code>rbowen</code>)
+ en el directorio. En la mayor&#237;a de los casos, se querr&#225; permitir el acceso
+ a m&#225;s de una persona. Aqu&#237; es donde la directiva
+ <code class="directive"><a href="../mod/mod_authz_groupfile.html#authgroupfile">AuthGroupFile</a></code> entra en juego.</p>
+
+ <p>Si lo que se desea es permitir a m&#225;s de una persona el acceso, necesitar&#225;s
+ crear un archivo de grupo que asocie los nombres de grupos con el de personas
+ para permitirles el acceso. El formato de este fichero es bastante sencillo,
+ y puedes crearlo con tu editor de texto favorito. El contenido del fichero
+ se parecer&#225; a:</p>
+
+ <div class="example"><p><code>
+ GroupName: rbowen dpitts sungo rshersey
+ </code></p></div>
+
+ <p>B&#225;sicamente eso es la lista de miembros los cuales est&#225;n en un mismo fichero
+ de grupo en una sola linea separados por espacios.</p>
+
+ <p>Para a&#241;adir un usuario a tu fichero de contrase&#241;as existente teclee:</p>
+
+ <div class="example"><p><code>
+ htpasswd /usr/local/apache/passwd/passwords dpitts
+ </code></p></div>
+
+ <p>Te responder&#225; lo mismo que anteriormente, pero se a&#241;adir&#225; al fichero
+ existente en vez de crear uno nuevo. (Es decir el flag <code>-c</code> ser&#225;
+ el que haga que se genere un nuevo
+ fichero de contrase&#241;as).</p>
+
+ <p>Ahora, tendr&#225; que modificar su fichero <code>.htaccess</code> para que sea
+ parecido a lo siguiente:</p>
+
+ <pre class="prettyprint lang-config">AuthType Basic
+AuthName "By Invitation Only"
+# Optional line:
+AuthBasicProvider file
+AuthUserFile "/usr/local/apache/passwd/passwords"
+AuthGroupFile "/usr/local/apache/passwd/groups"
+Require group GroupName</pre>
+
+
+ <p>Ahora, cualquiera que est&#233; listado en el grupo <code>GroupName</code>,
+ y tiene una entrada en el fichero de <code>contrase&#241;as</code>, se les
+ permitir&#225; el acceso, si introducen su contrase&#241;a correctamente.</p>
+
+ <p>Hay otra manera de dejar entrar a varios usuarios, que es menos espec&#237;fica.
+ En lugar de crear un archivo de grupo, s&#243;lo puede utilizar la siguiente
+ directiva:</p>
+
+ <pre class="prettyprint lang-config">Require valid-user</pre>
+
+
+ <p>Usando &#233;sto en vez de la l&#237;nea <code>Require user rbowen</code>
+ permitir&#225; a cualquier persona acceder, la cu&#225;l aparece en el archivo de
+ contrase&#241;as, y que introduzca correctamente su contrase&#241;a. Incluso puede
+ emular el comportamiento del grupo aqu&#237;, s&#243;lo manteniendo un fichero de
+ contrase&#241;as independiente para cada grupo. La ventaja de este enfoque es
+ que Apache s&#243;lo tiene que comprobar un archivo, en lugar de dos. La desventaja
+ es que se tiene que mantener un mont&#243;n de ficheros de contrase&#241;a de grupo, y
+ recuerde hacer referencia al fichero correcto en la directiva
+ <code class="directive"><a href="../mod/mod_authn_file.html#authuserfile">AuthUserFile</a></code>.</p>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="possibleproblems" id="possibleproblems">Posibles Problemas</a></h2>
+ <p>Debido a la forma en que se especifica la autenticaci&#243;n b&#225;sica,
+ su nombre de usuario y la contrase&#241;a deben ser verificados cada vez
+ que se solicita un documento desde el servidor. Esto es, incluso si&nbsp;
+ se&nbsp; vuelve a cargar la misma p&#225;gina, y para cada imagen de la p&#225;gina (si
+&nbsp;&nbsp;&nbsp;&nbsp;provienen de un directorio protegido). Como se puede imaginar, esto
+&nbsp;&nbsp;&nbsp;&nbsp;ralentiza las cosas un poco. La cantidad que ralentiza las cosas es
+ proporcional al tama&#241;o del archivo de contrase&#241;as, porque tiene que
+ abrir ese archivo, recorrer&nbsp;lista de usuarios hasta que llega a su nombre.
+ Y tiene que hacer esto cada vez que se carga una p&#225;gina.</p>
+
+ <p>Una consecuencia de esto, es que hay un limite pr&#225;ctico de cuantos
+ usuarios puedes introducir en el fichero de contrase&#241;as. Este l&#237;mite
+ variar&#225; dependiendo de la m&#225;quina en la que tengas el servidor,
+ pero puedes notar ralentizaciones en cuanto se metan cientos de entradas,
+ y por lo tanto consideraremos entonces otro m&#233;todo de autenticaci&#243;n
+ en ese momento.
+ </p>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="dbmdbd" id="dbmdbd">M&#233;todo alternativo de almacenamiento de las
+ contrase&#241;as</a></h2>
+
+ <p>Debido a que el almacenamiento de las contrase&#241;as en texto plano tiene
+ el problema mencionado anteriormente, puede que se prefiera guardar
+ las contrase&#241;as en otro lugar como por ejemplo una base de datos.
+ </p>
+
+ <p>Los m&#243;dulos <code class="module"><a href="../mod/mod_authn_dbm.html">mod_authn_dbm</a></code> y <code class="module"><a href="../mod/mod_authn_dbd.html">mod_authn_dbd</a></code> son
+ dos m&#243;dulos que hacen esto posible. En vez de seleccionar la directiva de fichero
+ <code><code class="directive"><a href="../mod/mod_auth_basic.html#authbasicprovider">AuthBasicProvider</a></code> </code>, en su lugar
+ se puede elegir <code>dbm</code> o <code>dbd</code> como formato de almacenamiento.</p>
+
+ <p>Para seleccionar los ficheros de tipo dbm en vez de texto plano, podremos hacer algo parecido a lo siguiente:</p>
+
+ <pre class="prettyprint lang-config">&lt;Directory "/www/docs/private"&gt;
+ AuthName "Private"
+ AuthType Basic
+ AuthBasicProvider dbm
+ AuthDBMUserFile "/www/passwords/passwd.dbm"
+ Require valid-user
+&lt;/Directory&gt;</pre>
+
+
+ <p>Hay otras opciones disponibles. Consulta la documentaci&#243;n de
+ <code class="module"><a href="../mod/mod_authn_dbm.html">mod_authn_dbm</a></code> para m&#225;s detalles.</p>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="multprovider" id="multprovider">Uso de m&#250;ltiples proveedores</a></h2>
+
+ <p>Con la introducci&#243;n de la nueva autenticaci&#243;n basada en un proveedor y
+ una arquitectura de autorizaci&#243;n, ya no estaremos restringidos a un &#250;nico
+ m&#233;todo de autenticaci&#243;n o autorizaci&#243;n. De hecho, cualquier n&#250;mero de
+ los proveedores pueden ser mezclados y emparejados para ofrecerle
+ exactamente el esquema que se adapte a sus necesidades.
+ En el siguiente ejemplo, veremos como ambos proveedores tanto el fichero
+ como el LDAP son usados en la autenticaci&#243;n:
+ </p>
+
+ <pre class="prettyprint lang-config">&lt;Directory "/www/docs/private"&gt;
+ AuthName "Private"
+ AuthType Basic
+ AuthBasicProvider file ldap
+ AuthUserFile "/usr/local/apache/passwd/passwords"
+ AuthLDAPURL ldap://ldaphost/o=yourorg
+ Require valid-user
+&lt;/Directory&gt;</pre>
+
+
+ <p>En este ejemplo el fichero, que act&#250;a como proveedor, intentar&#225; autenticar
+ primero al usuario. Si no puede autenticar al usuario, el proveedor del LDAP
+ ser&#225; llamado para que realice la autenticaci&#243;n.
+ Esto permite al &#225;mbito de autenticaci&#243;n ser amplio, si su organizaci&#243;n
+ implementa m&#225;s de un tipo de almac&#233;n de autenticaci&#243;n.
+ Otros escenarios de autenticaci&#243;n y autorizaci&#243;n pueden incluir la
+ mezcla de un tipo de autenticaci&#243;n con un tipo diferente de autorizaci&#243;n.
+ Por ejemplo, autenticar contra un fichero de contrase&#241;as pero autorizando
+ dicho acceso mediante el directorio del LDAP.</p>
+
+ <p>As&#237; como m&#250;ltiples m&#233;todos y proveedores de autenticaci&#243;n pueden
+ ser implementados, tambi&#233;n pueden usarse m&#250;ltiples formas de
+ autorizaci&#243;n.
+ En este ejemplo ambos ficheros de autorizaci&#243;n de grupo as&#237; como
+ autorizaci&#243;n de grupo mediante LDAP va a ser usado:
+ </p>
+
+ <pre class="prettyprint lang-config">&lt;Directory "/www/docs/private"&gt;
+ AuthName "Private"
+ AuthType Basic
+ AuthBasicProvider file
+ AuthUserFile "/usr/local/apache/passwd/passwords"
+ AuthLDAPURL ldap://ldaphost/o=yourorg
+ AuthGroupFile "/usr/local/apache/passwd/groups"
+ Require group GroupName
+ Require ldap-group cn=mygroup,o=yourorg
+&lt;/Directory&gt;</pre>
+
+
+ <p>Para llevar la autorizaci&#243;n un poco m&#225;s lejos, las directivas
+ de autorizaci&#243;n de contenedores tales como
+ <code class="directive"><a href="../mod/mod_authz_core.html#requireall">&lt;RequireAll&gt;</a></code>
+ and
+ <code class="directive"><a href="../mod/mod_authz_core.html#requireany">&lt;RequireAny&gt;</a></code>
+ nos permiten aplicar una l&#243;gica de en qu&#233; orden se manejar&#225; la autorizaci&#243;n dependiendo
+ de la configuraci&#243;n y controlada a trav&#233;s de ella.
+ Mire tambi&#233;n <a href="../mod/mod_authz_core.html#logic">Contenedores de
+ Autorizaci&#243;n</a> para ejemplos de c&#243;mo pueden ser aplicados.</p>
+
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="beyond" id="beyond">M&#225;s all&#225; de la Autorizaci&#243;n</a></h2>
+
+ <p>El modo en que la autorizaci&#243;n puede ser aplicada es ahora mucho m&#225;s flexible
+ que us solo chequeo contra un almac&#233;n de datos (contrase&#241;as). Ordenando la
+ l&#243;gica y escoger la forma en que la autorizaci&#243;n es realizada, ahora es posible
+ </p>
+
+ <h3><a name="authandororder" id="authandororder">Aplicando la l&#243;gica y ordenaci&#243;n</a></h3>
+ <p>Controlar el c&#243;mo y en qu&#233; orden se va a aplicar la autorizaci&#243;n ha
+ sido un misterio en el pasado. En Apache 2.2 un proveedor del
+ mecanismo de autenticaci&#243;n fue introducido para disociar el proceso actual
+ de autenticaci&#243;n y soportar funcionalidad.
+ Uno de los beneficios secundarios fue que los proveedores de autenticaci&#243;n
+ pod&#237;an ser configurados y llamados en un orden especifico que no dependieran
+ en el orden de carga del propio modulo.
+ Este proveedor de dicho mecanismo, ha sido introducido en la autorizaci&#243;n
+ tambi&#233;n. Lo que esto significa es que la directiva
+ <code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code>
+ no s&#243;lo especifica que m&#233;todo de autorizaci&#243;n deber&#225; ser usado, si no
+ tambi&#233;n especifica el orden en que van a ser llamados. M&#250;ltiples
+ m&#233;todos de autorizaci&#243;n son llamados en el mismo orden en que la directiva
+ <code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code> aparece en la
+ configuraci&#243;n.
+ </p>
+
+ <p>
+ Con la Introducci&#243;n del contenedor de directivas de autorizaci&#243;n tales como
+ <code class="directive"><a href="../mod/mod_authz_core.html#requireall">&lt;RequireAll&gt;</a></code>
+ y
+ <code class="directive"><a href="../mod/mod_authz_core.html#requireany">&lt;RequireAny&gt;</a></code>,
+ La configuraci&#243;n tambi&#233;n tiene control sobre cu&#225;ndo se llaman a los m&#233;todos
+ de autorizaci&#243;n y qu&#233; criterios determinan cu&#225;ndo se concede el acceso.
+ Vease
+ <a href="../mod/mod_authz_core.html#logic">Contenedores de autorizaci&#243;n</a>
+ Para un ejemplo de c&#243;mo pueden ser utilizados para expresar una l&#243;gica
+ m&#225;s compleja de autorizaci&#243;n.
+ </p>
+
+ <p>
+ Por defecto todas las directivas
+ <code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code>
+ son manejadas como si estuvieran contenidas en una directiva
+ <code class="directive"><a href="../mod/mod_authz_core.html#requireany">&lt;RequireAny&gt;</a></code>.
+ En otras palabras, Si alguno de los m&#233;todos de autorizaci&#243;n
+ especificados tiene &#233;xito, se concede la autorizaci&#243;n.
+ </p>
+
+
+
+ <h3><a name="reqaccessctrl" id="reqaccessctrl">Uso de los proveedores de autorizaci&#243;n para
+ el control de acceso</a></h3>
+
+ <p>
+ La autenticaci&#243;n de nombre de usuario y contrase&#241;a es s&#243;lo parte
+ de toda la historia que conlleva el proceso. Frecuentemente quiere
+ dar acceso a la gente en base a algo m&#225;s que lo que son.
+ Algo como de donde vienen.
+ </p>
+
+ <p>
+ Los proveedores de autorizaci&#243;n <code>all</code>,
+ <code>env</code>, <code>host</code> y <code>ip</code>
+ te permiten denegar o permitir el acceso bas&#225;ndose en otros
+ criterios como el nombre de la m&#225;quina o la IP de la m&#225;quina que
+ realiza la consulta para un documento.
+ </p>
+
+ <p>
+ El uso de estos proveedores se especifica a trav&#233;s de la directiva
+ <code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code>.
+ La directiva registra los proveedores de autorizaci&#243;n que ser&#225;n llamados
+ durante la solicitud de la fase del proceso de autorizaci&#243;n. Por ejemplo:
+ </p>
+
+ <pre class="prettyprint lang-config">Require ip <var>address</var>
+ </pre>
+
+
+ <p>
+ Donde <var>address</var> es una direcci&#243;n IP (o una direcci&#243;n IP parcial)
+ o bien:
+ </p>
+
+ <pre class="prettyprint lang-config">Require host <var>domain_name</var>
+ </pre>
+
+
+ <p>
+ Donde <var>domain_name</var> es el nombre completamente cualificado de un nombre
+ de dominio (FQDN) (o un nombre parcial del dominio);
+ puede proporcionar m&#250;ltiples direcciones o nombres de dominio, si se desea.
+ </p>
+
+ <p>
+ Por ejemplo, si alguien env&#237;a spam a su tabl&#243;n de mensajes y desea
+ mantenerlos alejados, podr&#237;a hacer lo siguiente:</p>
+
+ <pre class="prettyprint lang-config">&lt;RequireAll&gt;
+ Require all granted
+ Require not ip 10.252.46.165
+&lt;/RequireAll&gt;</pre>
+
+
+ <p>
+ Visitantes que vengan desde esa IP no ser&#225;n capaces de ver el contenido
+ que cubre esta directiva. Si, en cambio, lo que se tiene es el nombre de
+ la m&#225;quina, en vez de la direcci&#243;n IP, podr&#237;a usar:
+ </p>
+
+ <pre class="prettyprint lang-config">&lt;RequireAll&gt;
+ Require all granted
+ Require not host host.example.com
+&lt;/RequireAll&gt;</pre>
+
+
+ <p>
+ Y, si lo que se quiere es bloquear el acceso desde un determinado dominio
+ (bloquear el acceso desde el dominio entero), puede especificar parte
+ de la direcci&#243;n o del propio dominio a bloquear:
+ </p>
+
+ <pre class="prettyprint lang-config">&lt;RequireAll&gt;
+ Require all granted
+ Require not ip 192.168.205
+ Require not host phishers.example.com moreidiots.example
+ Require not host ke
+&lt;/RequireAll&gt;</pre>
+
+
+ <p>
+ Usando <code class="directive"><a href="../mod/mod_authz_core.html#requireall">&lt;RequireAll&gt;</a></code>
+ con m&#250;ltiples directivas <code class="directive"><a href="../mod/mod_authz_core.html#require">&lt;Require&gt;</a></code>, cada una negada con un <code>not</code>,
+ S&#243;lo permitir&#225; el acceso, si todas las condiciones negadas son verdaderas.
+ En otras palabras, el acceso ser&#225; bloqueado, si cualquiera de las condiciones
+ negadas fallara.
+ </p>
+
+
+
+ <h3><a name="filesystem" id="filesystem">Compatibilidad de Control de Acceso con versiones
+ anteriores </a></h3>
+
+ <p>
+ Uno de los efectos secundarios de adoptar proveedores basados en
+ mecanismos de autenticaci&#243;n es que las directivas anteriores
+ <code class="directive"><a href="../mod/mod_access_compat.html#order">Order</a></code>,
+ <code class="directive"><a href="../mod/mod_access_compat.html#allow">Allow</a></code>,
+ <code class="directive"><a href="../mod/mod_access_compat.html#deny">Deny</a></code> y
+ <code class="directive"><a href="../mod/mod_access_compat.html#satisfy">Satisfy</a></code> ya no son necesarias.
+ Sin embargo, para proporcionar compatibilidad con configuraciones antiguas,
+ estas directivas se han movido al m&#243;dulo <code class="module"><a href="../mod/mod_access_compat.html">mod_access_compat</a></code>.
+ </p>
+
+ <div class="warning"><h3>Nota:</h3>
+ <p>
+ Las directivas proporcionadas por <code class="module"><a href="../mod/mod_access_compat.html">mod_access_compat</a></code>
+ han quedado obsoletas por <code class="module"><a href="../mod/mod_authz_host.html">mod_authz_host</a></code>. Mezclar
+ directivas antiguas como
+ <code class="directive"><a href="../mod/mod_access_compat.html#order">Order</a></code>,
+ <code class="directive"><a href="../mod/mod_access_compat.html#allow">Allow</a></code> &#243;
+ <code class="directive"><a href="../mod/mod_access_compat.html#deny">Deny</a></code> con las nuevas
+ como
+ <code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code>
+ es t&#233;cnicamente posible pero desaconsejable. El m&#243;dulo
+ <code class="module"><a href="../mod/mod_access_compat.html">mod_access_compat</a></code> se cre&#243; para soportar configuraciones
+ que contuvieran s&#243;lo directivas antiguas para facilitar la actualizaci&#243;n
+ a la versi&#243;n 2.4.
+ Por favor revise la documentaci&#243;n de
+ <a href="../upgrading.html">actualizaci&#243;n</a> para m&#225;s informaci&#243;n al
+ respecto.
+ </p>
+ </div>
+
+
+ </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="socache" id="socache">Cache de Autenticaci&#243;n</a></h2>
+ <p>
+ Puede haber momentos en que la autenticaci&#243;n ponga una carga
+ inaceptable en el proveedor (de autenticaci&#243;n) o en tu red.
+ Esto suele afectar a los usuarios de <code class="module"><a href="../mod/mod_authn_dbd.html">mod_authn_dbd</a></code>
+ (u otros proveedores de terceros/personalizados).
+ Para lidiar con este problema, HTTPD 2.3/2.4 introduce un nuevo proveedor
+ de cach&#233; <code class="module"><a href="../mod/mod_authn_socache.html">mod_authn_socache</a></code> para cachear las credenciales
+ y reducir la carga en el proveedor(es) original.
+ </p>
+ <p>
+ Esto puede ofrecer un aumento de rendimiento sustancial para algunos usuarios.
+ </p>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="moreinformation" id="moreinformation">M&#225;s informaci&#243;n</a></h2>
+
+ <p>
+ Tambi&#233;n deber&#237;a leer la documentaci&#243;n para
+ <code class="module"><a href="../mod/mod_auth_basic.html">mod_auth_basic</a></code> y <code class="module"><a href="../mod/mod_authz_host.html">mod_authz_host</a></code>
+ la cu&#225;l contiene m&#225;s informaci&#243;n de como funciona todo esto.
+ La directiva <code class="directive"><a href="../mod/mod_authn_core.html#authnprovideralias">&lt;AuthnProviderAlias&gt;</a></code> puede tambi&#233;n ayudar
+ a la hora de simplificar ciertas configuraciones de autenticaci&#243;n.
+ </p>
+
+ <p>
+ Los diferentes algoritmos de cifrado que est&#225;n soportados por Apache
+ para la autenticaci&#243;n se explican en
+ <a href="../misc/password_encryptions.html">Cifrado de Contrase&#241;as</a>.
+ </p>
+
+ <p>
+ Y tal vez quiera ojear la documentaci&#243;n de "how to"
+ <a href="access.html">Control de Acceso</a> donde se mencionan temas
+ relacionados.</p>
+
+</div></div>
+<div class="bottomlang">
+<p><span>Idiomas disponibles: </span><a href="../en/howto/auth.html" hreflang="en" rel="alternate" title="English">&nbsp;en&nbsp;</a> |
+<a href="../es/howto/auth.html" title="Espa&#241;ol">&nbsp;es&nbsp;</a> |
+<a href="../fr/howto/auth.html" hreflang="fr" rel="alternate" title="Fran&#231;ais">&nbsp;fr&nbsp;</a> |
+<a href="../ja/howto/auth.html" hreflang="ja" rel="alternate" title="Japanese">&nbsp;ja&nbsp;</a> |
+<a href="../ko/howto/auth.html" hreflang="ko" rel="alternate" title="Korean">&nbsp;ko&nbsp;</a> |
+<a href="../tr/howto/auth.html" hreflang="tr" rel="alternate" title="T&#252;rk&#231;e">&nbsp;tr&nbsp;</a></p>
+</div><div class="top"><a href="#page-header"><img src="../images/up.gif" alt="top" /></a></div><div class="section"><h2><a id="comments_section" name="comments_section">Comentarios</a></h2><div class="warning"><strong>Notice:</strong><br />This is not a Q&amp;A section. Comments placed here should be pointed towards suggestions on improving the documentation or server, and may be removed by our moderators if they are either implemented or considered invalid/off-topic. Questions on how to manage the Apache HTTP Server should be directed at either our IRC channel, #httpd, on Libera.chat, or sent to our <a href="https://httpd.apache.org/lists.html">mailing lists</a>.</div>
+<script type="text/javascript"><!--//--><![CDATA[//><!--
+var comments_shortname = 'httpd';
+var comments_identifier = 'http://httpd.apache.org/docs/2.4/howto/auth.html';
+(function(w, d) {
+ if (w.location.hostname.toLowerCase() == "httpd.apache.org") {
+ d.write('<div id="comments_thread"><\/div>');
+ var s = d.createElement('script');
+ s.type = 'text/javascript';
+ s.async = true;
+ s.src = 'https://comments.apache.org/show_comments.lua?site=' + comments_shortname + '&page=' + comments_identifier;
+ (d.getElementsByTagName('head')[0] || d.getElementsByTagName('body')[0]).appendChild(s);
+ }
+ else {
+ d.write('<div id="comments_thread">Comments are disabled for this page at the moment.<\/div>');
+ }
+})(window, document);
+//--><!]]></script></div><div id="footer">
+<p class="apache">Copyright 2023 The Apache Software Foundation.<br />Licencia bajo los t&#233;rminos de la <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p>
+<p class="menu"><a href="../mod/">M&#243;dulos</a> | <a href="../mod/directives.html">Directivas</a> | <a href="http://wiki.apache.org/httpd/FAQ">Preguntas Frecuentes</a> | <a href="../glossary.html">Glosario</a> | <a href="../sitemap.html">Mapa del sitio web</a></p></div><script type="text/javascript"><!--//--><![CDATA[//><!--
+if (typeof(prettyPrint) !== 'undefined') {
+ prettyPrint();
+}
+//--><!]]></script>
+</body></html> \ No newline at end of file
diff --git a/docs/manual/howto/auth.html.fr.utf8 b/docs/manual/howto/auth.html.fr.utf8
new file mode 100644
index 0000000..760a222
--- /dev/null
+++ b/docs/manual/howto/auth.html.fr.utf8
@@ -0,0 +1,681 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="fr" xml:lang="fr"><head>
+<meta content="text/html; charset=UTF-8" http-equiv="Content-Type" />
+<!--
+ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+ This file is generated from xml source: DO NOT EDIT
+ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+ -->
+<title>Authentification et autorisation - Serveur HTTP Apache Version 2.4</title>
+<link href="../style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" />
+<link href="../style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" />
+<link href="../style/css/manual-print.css" rel="stylesheet" media="print" type="text/css" /><link rel="stylesheet" type="text/css" href="../style/css/prettify.css" />
+<script src="../style/scripts/prettify.min.js" type="text/javascript">
+</script>
+
+<link href="../images/favicon.ico" rel="shortcut icon" /></head>
+<body id="manual-page"><div id="page-header">
+<p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a> | <a href="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="../glossary.html">Glossaire</a> | <a href="../sitemap.html">Plan du site</a></p>
+<p class="apache">Serveur HTTP Apache Version 2.4</p>
+<img alt="" src="../images/feather.png" /></div>
+<div class="up"><a href="./"><img title="&lt;-" alt="&lt;-" src="../images/left.gif" /></a></div>
+<div id="path">
+<a href="http://www.apache.org/">Apache</a> &gt; <a href="http://httpd.apache.org/">Serveur HTTP</a> &gt; <a href="http://httpd.apache.org/docs/">Documentation</a> &gt; <a href="../">Version 2.4</a> &gt; <a href="./">Recettes / Tutoriels</a></div><div id="page-content"><div id="preamble"><h1>Authentification et autorisation</h1>
+<div class="toplang">
+<p><span>Langues Disponibles: </span><a href="../en/howto/auth.html" hreflang="en" rel="alternate" title="English">&nbsp;en&nbsp;</a> |
+<a href="../es/howto/auth.html" hreflang="es" rel="alternate" title="Espa簽ol">&nbsp;es&nbsp;</a> |
+<a href="../fr/howto/auth.html" title="Fran癟ais">&nbsp;fr&nbsp;</a> |
+<a href="../ja/howto/auth.html" hreflang="ja" rel="alternate" title="Japanese">&nbsp;ja&nbsp;</a> |
+<a href="../ko/howto/auth.html" hreflang="ko" rel="alternate" title="Korean">&nbsp;ko&nbsp;</a> |
+<a href="../tr/howto/auth.html" hreflang="tr" rel="alternate" title="T羹rk癟e">&nbsp;tr&nbsp;</a></p>
+</div>
+
+ <p>L'authentification est un processus qui vous permet de v矇rifier
+ qu'une personne est bien celle qu'elle pr矇tend 礙tre. L'autorisation
+ est un processus qui permet une personne d'aller l o羅 elle veut
+ aller, ou d'obtenir les informations qu'elle d矇sire.</p>
+
+ <p>Pour le contr繫le d'acc癡s en g矇n矇ral, voir le How-To <a href="access.html">Contr繫le d'acc癡s</a>.</p>
+</div>
+<div id="quickview"><a href="https://www.apache.org/foundation/contributing.html" class="badge"><img src="https://www.apache.org/images/SupportApache-small.png" alt="Support Apache!" /></a><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#related">Modules et directives concern矇s</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#introduction">Introduction</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#theprerequisites">Les pr矇requis</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#gettingitworking">Mise en oeuvre</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#lettingmorethanonepersonin">Autorisation d'acc癡s
+plusieurs personnes</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#possibleproblems">Probl癡mes possibles</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#dbmdbd">Autre m矇thode de stockage des mots de
+passe</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#multprovider">Utilisation de plusieurs fournisseurs
+d'authentification</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#beyond">Pour aller plus loin qu'une simple
+autorisation</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#socache">Mise en cache de l'authentification</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#moreinformation">Pour aller plus loin . . .</a></li>
+</ul><h3>Voir aussi</h3><ul class="seealso"><li><a href="#comments_section">Commentaires</a></li></ul></div>
+<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="related" id="related">Modules et directives concern矇s</a></h2>
+
+<p>Trois groupes de modules sont concern矇s par le processus
+d'authentification et d'autorisation. Vous devrez utiliser au moins un
+module de chaque groupe.</p>
+
+<ul>
+ <li>Type d'authentification (voir la directive <code class="directive"><a href="../mod/mod_authn_core.html#authtype">AuthType</a></code>)
+ <ul>
+ <li><code class="module"><a href="../mod/mod_auth_basic.html">mod_auth_basic</a></code></li>
+ <li><code class="module"><a href="../mod/mod_auth_digest.html">mod_auth_digest</a></code></li>
+ </ul>
+ </li>
+ <li>Fournisseur d'authentification (voir les directives <code class="directive"><a href="../mod/mod_auth_basic.html#authbasicprovider">AuthBasicProvider</a></code> et <code class="directive"><a href="../mod/mod_auth_digest.html#authdigestprovider">AuthDigestProvider</a></code>)
+
+ <ul>
+ <li><code class="module"><a href="../mod/mod_authn_anon.html">mod_authn_anon</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authn_dbd.html">mod_authn_dbd</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authn_dbm.html">mod_authn_dbm</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authn_file.html">mod_authn_file</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authnz_ldap.html">mod_authnz_ldap</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authn_socache.html">mod_authn_socache</a></code></li>
+ </ul>
+ </li>
+ <li>Autorisation (voir la directive <code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code>)
+ <ul>
+ <li><code class="module"><a href="../mod/mod_authnz_ldap.html">mod_authnz_ldap</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authz_dbd.html">mod_authz_dbd</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authz_dbm.html">mod_authz_dbm</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authz_groupfile.html">mod_authz_groupfile</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authz_host.html">mod_authz_host</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authz_owner.html">mod_authz_owner</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authz_user.html">mod_authz_user</a></code></li>
+ </ul>
+ </li>
+</ul>
+
+ <p>On peut aussi ajouter <code class="module"><a href="../mod/mod_authn_core.html">mod_authn_core</a></code> et
+ <code class="module"><a href="../mod/mod_authz_core.html">mod_authz_core</a></code>. Ces modules impl矇mentent des
+ directives g矇n矇rales qui op癡rent au dessus de tous les modules
+ d'authentification.</p>
+
+ <p>Le module <code class="module"><a href="../mod/mod_authnz_ldap.html">mod_authnz_ldap</a></code> est un fournisseur
+ d'authentification et d'autorisation. Le module
+ <code class="module"><a href="../mod/mod_authz_host.html">mod_authz_host</a></code> fournit une autorisation et un
+ contr繫le d'acc癡s bas矇s sur le nom du serveur, l'adresse IP ou
+ certaines caract矇ristiques de la requ礙te, mais ne fait pas partie du
+ syst癡me fournisseur d'authentification. Le module
+ <code class="module"><a href="../mod/mod_access_compat.html">mod_access_compat</a></code> a 矇t矇 cr矇矇 des fins de
+ compatibilit矇 ascendante avec mod_access.</p>
+
+ <p>Vous devriez aussi jeter un coup d'oeil au manuel de recettes de <a href="access.html">Contr繫le d'acc癡s</a>, qui d矇crit les diff矇rentes
+ m矇thodes de contr繫le d'acc癡s votre serveur.</p>
+
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="introduction" id="introduction">Introduction</a></h2>
+ <p>Si votre site web contient des informations sensibles ou
+ destin矇es seulement un groupe de personnes restreint, les
+ techniques expos矇es dans cet article vont vous aider vous assurer
+ que les personnes qui ont acc癡s ces pages sont bien celles
+ auxquelles vous avez donn矇 l'autorisation d'acc癡s.</p>
+
+ <p>Cet article d矇crit les m矇thodes "standards" de protection de
+ parties de votre site web que la plupart d'entre vous sont appel矇s
+ utiliser.</p>
+
+ <div class="note"><h3>Note :</h3>
+ <p>Si vos donn矇es ont un r矇el besoin de s矇curisation, pr矇voyez
+ l'utilisation de <code class="module"><a href="../mod/mod_ssl.html">mod_ssl</a></code> en plus de toute m矇thode
+ d'authentification.</p>
+ </div>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="theprerequisites" id="theprerequisites">Les pr矇requis</a></h2>
+ <p>Les directives d矇crites dans cet article devront 礙tre ins矇r矇es
+ soit au niveau de la configuration de votre serveur principal (en
+ g矇n矇ral dans une section <code class="directive"><a href="../mod/core.html#directory">&lt;Directory&gt;</a></code>), soit au niveau de la
+ configuration des r矇pertoires (fichiers <code>.htaccess</code>)</p>
+
+ <p>Si vous envisagez l'utilisation de fichiers
+ <code>.htaccess</code>, la configuration de votre serveur devra
+ permettre l'ajout de directives d'authentification dans ces
+ fichiers. Pour ce faire, on utilise la directive <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code>, qui sp矇cifie quelles
+ directives pourront 矇ventuellement contenir les fichiers de
+ configuration de niveau r矇pertoire.</p>
+
+ <p>Comme il est ici question d'authentification, vous aurez besoin
+ d'une directive <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code>
+ du style :</p>
+
+ <pre class="prettyprint lang-config">AllowOverride AuthConfig</pre>
+
+
+ <p>Si vous avez l'intention d'ajouter les directives directement
+ dans le fichier de configuration principal, vous devrez bien entendu
+ poss矇der les droits en 矇criture sur ce fichier.</p>
+
+ <p>Vous devrez aussi conna簾tre un tant soit peu la structure des
+ r矇pertoires de votre serveur, ne serait-ce que pour savoir o羅 se
+ trouvent certains fichiers. Cela ne devrait pas pr矇senter de grandes
+ difficult矇s, et nous essaierons de clarifier tout 癟a lorsque le besoin
+ s'en fera sentir.</p>
+
+ <p>Enfin, vous devrez vous assurer que les modules
+ <code class="module"><a href="../mod/mod_authn_core.html">mod_authn_core</a></code> et <code class="module"><a href="../mod/mod_authz_core.html">mod_authz_core</a></code>
+ ont 矇t矇 soit compil矇s avec le binaire httpd, soit charg矇s par le
+ fichier de configuration httpd.conf. Ces deux modules fournissent
+ des directives g矇n矇rales et des fonctionnalit矇s qui sont critiques
+ quant la configuration et l'utilisation de l'authentification et
+ de l'autorisation au sein du serveur web.</p>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="gettingitworking" id="gettingitworking">Mise en oeuvre</a></h2>
+ <p>Nous d矇crivons ici les bases de la protection par mot de passe
+ d'un r矇pertoire de votre serveur.</p>
+
+ <p>Vous devez en premier lieu cr矇er un fichier de mots de passe. La
+ m矇thode exacte selon laquelle vous allez cr矇er ce fichier va varier
+ en fonction du fournisseur d'authentification choisi. Mais nous
+ entrerons dans les d矇tails plus loin, et pour le moment, nous nous
+ contenterons d'un fichier de mots de passe en mode texte.</p>
+
+ <p>Ce fichier doit 礙tre enregistr矇 un endroit non accessible
+ depuis le web, de fa癟on ce que les clients ne puissent pas le
+ t矇l矇charger. Par exemple, si vos documents sont servis partir de
+ <code>/usr/local/apache/htdocs</code>, vous pouvez enregistrer le
+ fichier des mots de passe dans
+ <code>/usr/local/apache/passwd</code>.</p>
+
+ <p>L'utilitaire <code class="program"><a href="../programs/htpasswd.html">htpasswd</a></code> fourni avec Apache
+ permet de cr矇er ce fichier. Vous le trouverez dans le r矇pertoire
+ <code>bin</code> de votre installation d'Apache. Si vous avez
+ install矇 Apache partir d'un paquetage tiers, il sera probablement
+ dans le chemin par d矇faut de vos ex矇cutables.</p>
+
+ <p>Pour cr矇er le fichier, tapez :</p>
+
+ <div class="example"><p><code>
+ htpasswd -c /usr/local/apache/passwd/passwords rbowen
+ </code></p></div>
+
+ <p><code class="program"><a href="../programs/htpasswd.html">htpasswd</a></code> vous demandera d'entrer le mot de
+ passe, et de le retaper pour confirmation :</p>
+
+ <div class="example"><p><code>
+ # htpasswd -c /usr/local/apache/passwd/passwords rbowen<br />
+ New password: mot-de-passe<br />
+ Re-type new password: mot-de-passe<br />
+ Adding password for user rbowen
+ </code></p></div>
+
+ <p>Si <code class="program"><a href="../programs/htpasswd.html">htpasswd</a></code> n'est pas dans le chemin par
+ d矇faut de vos ex矇cutables, vous devrez bien entendu entrer le chemin
+ complet du fichier. Dans le cas d'une installation par d矇faut, il se
+ trouve <code>/usr/local/apache2/bin/htpasswd</code>.</p>
+
+ <p>Ensuite, vous allez devoir configurer le serveur de fa癟on ce
+ qu'il demande un mot de passe et lui pr矇ciser quels utilisateurs ont
+ l'autorisation d'acc癡s. Pour ce faire, vous pouvez soit 矇diter le
+ fichier <code>httpd.conf</code>, soit utiliser un fichier
+ <code>.htaccess</code>. Par exemple, si vous voulez prot矇ger le
+ r矇pertoire <code>/usr/local/apache/htdocs/secret</code>, vous pouvez
+ utiliser les directives suivantes, soit dans le fichier
+ <code>/usr/local/apache/htdocs/secret/.htaccess</code>, soit dans le
+ fichier <code>httpd.conf</code> l'int矇rieur d'une section &lt;Directory
+ "/usr/local/apache/htdocs/secret"&gt; :</p>
+
+ <pre class="prettyprint lang-config">AuthType Basic
+AuthName "Restricted Files"
+# (Following line optional)
+AuthBasicProvider file
+AuthUserFile "/usr/local/apache/passwd/passwords"
+Require user rbowen</pre>
+
+
+ <p>Examinons ces directives une une. La directive <code class="directive"><a href="../mod/mod_authn_core.html#authtype">AuthType</a></code> d矇finit la m矇thode
+ utilis矇e pour authentifier l'utilisateur. La m矇thode la plus
+ courante est <code>Basic</code>, et elle est impl矇ment矇e par
+ <code class="module"><a href="../mod/mod_auth_basic.html">mod_auth_basic</a></code>. Il faut cependant garder l'esprit
+ que l'authentification Basic transmet le mot de passe depuis le
+ client vers le serveur en clair. Cette m矇thode ne devra donc pas
+ 礙tre utilis矇e pour la transmission de donn矇es hautement sensibles si
+ elle n'est pas associ矇e au module <code class="module"><a href="../mod/mod_ssl.html">mod_ssl</a></code>. Apache
+ supporte une autre m矇thode d'authentification : <code>AuthType
+ Digest</code>. Cette m矇thode est impl矇ment矇e par le module <code class="module"><a href="../mod/mod_auth_digest.html">mod_auth_digest</a></code> et a 矇t矇 con癟ue pour
+ am矇liorer la s矇curit矇. Ce but n'a cependant pas 矇t矇 atteint et il est pr矇f矇rable
+ de chiffrer la connexion avec <code class="module"><a href="../mod/mod_ssl.html">mod_ssl</a></code>.</p>
+
+ <p>La directive <code class="directive"><a href="../mod/mod_authn_core.html#authname">AuthName</a></code> d矇finit
+ l'<dfn>Identificateur</dfn> (Realm) utiliser avec
+ l'authentification. L'identificateur poss癡de deux fonctions. Tout
+ d'abord, le client pr矇sente en g矇n矇ral cette information
+ l'utilisateur dans le cadre de la bo簾te de dialogue de mot de passe.
+ Ensuite, le client l'utilise pour d矇terminer quel mot de passe
+ envoyer pour une zone authentifi矇e donn矇e.</p>
+
+ <p>Ainsi par exemple, une fois un client authentifi矇 dans la zone
+ <code>"Fichiers r矇serv矇s"</code>, il soumettra nouveau
+ automatiquement le m礙me mot de passe pour toute zone du m礙me serveur
+ marqu矇e de l'identificateur <code>"Fichiers r矇serv矇s"</code>. De
+ cette fa癟on, vous pouvez 矇viter un utilisateur d'avoir saisir
+ plusieurs fois le m礙me mot de passe en faisant partager le m礙me
+ identificateur entre plusieurs zones r矇serv矇es. Bien entendu et pour
+ des raisons de s矇curit矇, le client devra redemander le mot
+ de passe chaque fois que le nom d'h繫te du serveur sera modifi矇.</p>
+
+ <p>La directive <code class="directive"><a href="../mod/mod_auth_basic.html#authbasicprovider">AuthBasicProvider</a></code> est, dans ce
+ cas, facultative, car <code>file</code> est la valeur par d矇faut
+ pour cette directive. Par contre, cette directive sera obligatoire
+ si vous utilisez une autre source d'authentification comme
+ <code class="module"><a href="../mod/mod_authn_dbm.html">mod_authn_dbm</a></code> ou
+ <code class="module"><a href="../mod/mod_authn_dbd.html">mod_authn_dbd</a></code>.</p>
+
+ <p>La directive <code class="directive"><a href="../mod/mod_authn_file.html#authuserfile">AuthUserFile</a></code> d矇finit le chemin
+ du fichier de mots de passe que nous venons de cr矇er avec
+ <code class="program"><a href="../programs/htpasswd.html">htpasswd</a></code>. Si vous poss矇dez un grand nombre
+ d'utilisateurs, la dur矇e de la recherche dans un fichier texte pour
+ authentifier un utilisateur chaque requ礙te va augmenter
+ rapidement, et pour pallier cet inconv矇nient, Apache peut aussi
+ stocker les donn矇es relatives aux
+ utilisateurs dans des bases de donn矇es rapides. Le module
+ <code class="module"><a href="../mod/mod_authn_dbm.html">mod_authn_dbm</a></code> fournit la directive <code class="directive"><a href="../mod/mod_authn_dbm.html#authdbmuserfile">AuthDBMUserFile</a></code>. Les programmes <code class="program"><a href="../programs/dbmmanage.html">dbmmanage</a></code> et <code class="program"><a href="../programs/htdbm.html">htdbm</a></code> permettent de
+ cr矇er et manipuler ces fichiers. Enfin, de nombreux modules tiers
+ fournissent d'autres types d'authentification.</p>
+
+ <p>Enfin, la directive <code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code> impl矇mente la partie
+ autorisation du processus en d矇finissant l'utilisateur autoris矇
+ acc矇der cette zone du serveur. Dans la section suivante, nous
+ d矇crirons les diff矇rentes m矇thodes d'utilisation de la directive
+ <code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code>.</p>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="lettingmorethanonepersonin" id="lettingmorethanonepersonin">Autorisation d'acc癡s
+plusieurs personnes</a></h2>
+ <p>Les directives ci-dessus n'autorisent qu'une personne (quelqu'un
+ poss矇dant le nom d'utilisateur <code>rbowen</code>) acc矇der au
+ r矇pertoire. Dans la plupart des cas, vous devrez autoriser
+ l'acc癡s plusieurs personnes. C'est ici
+ qu'intervient la directive <code class="directive"><a href="../mod/mod_authz_groupfile.html#authgroupfile">AuthGroupFile</a></code>.</p>
+
+ <p>Si vous voulez autoriser l'acc癡s plusieurs personnes, vous
+ devez cr矇er un fichier de groupes qui associe des noms de groupes
+ avec une liste d'utilisateurs de ce groupe. Le format de ce fichier
+ est tr癡s simple, et vous pouvez le cr矇er avec votre 矇diteur favori.
+ Son contenu se pr矇sente comme suit :</p>
+
+ <div class="example"><p><code>
+ Nom-de-groupe: rbowen dpitts sungo rshersey
+ </code></p></div>
+
+ <p>Il s'agit simplement une liste des membres du groupe sous la
+ forme d'une ligne s矇par矇e par des espaces.</p>
+
+ <p>Pour ajouter un utilisateur votre fichier de mots de passe
+ pr矇existant, entrez :</p>
+
+ <div class="example"><p><code>
+ htpasswd /usr/local/apache/passwd/passwords dpitts
+ </code></p></div>
+
+ <p>Vous obtiendrez le m礙me effet qu'auparavant, mais le mot de passe
+ sera ajout矇 au fichier, plut繫t que d'en cr矇er un nouveau (C'est le
+ drapeau <code>-c</code> qui permet de cr矇er un nouveau fichier de
+ mots de passe)..</p>
+
+ <p>Maintenant, vous devez modifier votre fichier
+ <code>.htaccess</code> ou la section <code class="directive"><a href="../mod/core.html#directory">&lt;Directory&gt;</a></code> comme suit :</p>
+
+ <pre class="prettyprint lang-config">AuthType Basic
+AuthName "By Invitation Only"
+# Optional line:
+AuthBasicProvider file
+AuthUserFile "/usr/local/apache/passwd/passwords"
+AuthGroupFile "/usr/local/apache/passwd/groups"
+Require group GroupName</pre>
+
+
+ <p>Maintenant, quiconque appartient au groupe
+ <code>Nom-de-groupe</code>, et poss癡de une entr矇e dans le fichier
+ <code>password</code> pourra acc矇der au r矇pertoire s'il tape le bon
+ mot de passe.</p>
+
+ <p>Il existe une autre m矇thode moins contraignante pour autoriser
+ l'acc癡s plusieurs personnes. Plut繫t que de cr矇er un fichier de
+ groupes, il vous suffit d'ajouter la directive suivante :</p>
+
+ <pre class="prettyprint lang-config">Require valid-user</pre>
+
+
+ <p>Le remplacement de la ligne <code>Require user rbowen</code> par
+ la ligne <code>Require valid-user</code> autorisera l'acc癡s
+ quiconque poss矇dant une entr矇e dans le fichier password, et ayant
+ tap矇 le bon mot de passe.</p>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="possibleproblems" id="possibleproblems">Probl癡mes possibles</a></h2>
+ <p>L'authentification Basic est sp矇cifi矇e d'une telle mani癡re que
+ vos nom d'utilisateur et mot de passe doivent 礙tre v矇rifi矇s chaque
+ fois que vous demandez un document au serveur, et ceci m礙me si vous
+ rechargez la m礙me page, et pour chaque image contenue dans la page
+ (si elles sont situ矇es dans un r矇pertoire prot矇g矇). Comme vous
+ pouvez l'imaginer, ceci ralentit un peu le fonctionnement. La mesure
+ dans laquelle le fonctionnement est ralenti est proportionnelle la
+ taille du fichier des mots de passe, car ce dernier doit 礙tre ouvert
+ et la liste des utilisateurs parcourue jusqu' ce que votre nom soit
+ trouv矇, et ceci chaque fois qu'une page est charg矇e.</p>
+
+ <p>En cons矇quence, ce ralentissement impose une limite pratique au
+ nombre d'utilisateurs que vous pouvez enregistrer dans un fichier de
+ mots de passe. Cette limite va varier en fonction des performances
+ de votre serveur, mais vous commencerez remarquer un
+ ralentissement lorsque vous atteindrez quelques centaines
+ d'utilisateurs, et serez alors appel矇s utiliser une m矇thode
+ d'authentification diff矇rente.</p>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="dbmdbd" id="dbmdbd">Autre m矇thode de stockage des mots de
+passe</a></h2>
+
+ <p>Suite au probl癡me 矇voqu矇 pr矇c矇demment et induit par le stockage
+ des mots de passe dans un fichier texte, vous pouvez 礙tre appel矇
+ stocker vos mots de passe d'une autre mani癡re, par exemple dans une
+ base de donn矇es.</p>
+
+ <p>Pour y parvenir, on peut utiliser les modules
+ <code class="module"><a href="../mod/mod_authn_dbm.html">mod_authn_dbm</a></code> ou <code class="module"><a href="../mod/mod_authn_dbd.html">mod_authn_dbd</a></code>.
+ Vous pouvez choisir comme format de stockage <code>dbm</code> ou
+ <code>dbd</code> la place de <code>file</code> pour la directive
+ <code class="directive"><a href="../mod/mod_auth_basic.html#authbasicprovider">AuthBasicProvider</a></code>.</p>
+
+ <p>Par exemple, pour s矇lectionner un fichier dbm la place d'un
+ fichier texte :</p>
+
+ <pre class="prettyprint lang-config">&lt;Directory "/www/docs/private"&gt;
+
+ AuthName "Private"
+ AuthType Basic
+ AuthBasicProvider dbm
+ AuthDBMUserFile "/www/passwords/passwd.dbm"
+ Require valid-user
+
+&lt;/Directory&gt;</pre>
+
+
+ <p>D'autres options sont disponibles. Consultez la documentation de
+ <code class="module"><a href="../mod/mod_authn_dbm.html">mod_authn_dbm</a></code> pour plus de d矇tails.</p>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="multprovider" id="multprovider">Utilisation de plusieurs fournisseurs
+d'authentification</a></h2>
+
+ <p>Depuis l'arriv矇e des nouvelles architecture d'autorisation et
+ d'authentification bas矇es sur les fournisseurs, vous n'礙tes plus
+ limit矇 une m矇thode d'authentification et d'autorisation
+ unique. En fait, on peut panacher autant de fournisseurs que l'on
+ veut, ce qui vous permet d'矇laborer l'architecture qui correspond
+ exactement vos besoins. Dans l'exemple suivant, on utilise
+ conjointement les fournisseurs d'authentification
+ file et LDAP :</p>
+
+ <pre class="prettyprint lang-config">&lt;Directory "/www/docs/private"&gt;
+
+ AuthName "Private"
+ AuthType Basic
+ AuthBasicProvider file ldap
+ AuthUserFile "/usr/local/apache/passwd/passwords"
+ AuthLDAPURL ldap://ldaphost/o=yourorg
+ Require valid-user
+
+&lt;/Directory&gt;</pre>
+
+
+ <p>Dans cet exemple, le fournisseur file va tenter d'authentifier
+ l'utilisateur en premier. S'il n'y parvient pas, le fournisseur LDAP
+ sera sollicit矇. Ceci permet l'矇largissement des possibilit矇s
+ d'authentification si votre organisation impl矇mente plusieurs types
+ de bases d'authentification. D'autres sc矇narios d'authentification
+ et d'autorisation peuvent associer un type d'authentification avec
+ un autre type d'autorisation. Par exemple, une authentification
+ bas矇e sur un fichier de mots de passe peut permettre l'attribution
+ d'autorisations bas矇e sur un annuaire LDAP.</p>
+
+ <p>Tout comme plusieurs fournisseurs d'authentification peuvent 礙tre
+ impl矇ment矇s, on peut aussi utiliser plusieurs m矇thodes
+ d'autorisation. Dans l'exemple suivant, on utilise la fois une
+ autorisation base de fichier de groupes et une autorisation base
+ de groupes LDAP.</p>
+
+ <pre class="prettyprint lang-config">&lt;Directory "/www/docs/private"&gt;
+
+ AuthName "Private"
+ AuthType Basic
+ AuthBasicProvider file
+ AuthUserFile "/usr/local/apache/passwd/passwords"
+ AuthLDAPURL ldap://ldaphost/o=yourorg
+ AuthGroupFile "/usr/local/apache/passwd/groups"
+ Require group GroupName
+ Require ldap-group cn=mygroup,o=yourorg
+
+&lt;/Directory&gt;</pre>
+
+
+ <p>Pour un sc矇nario d'autorisation un peu plus avanc矇, des
+ directives de conteneur d'autorisation comme <code class="directive"><a href="../mod/mod_authz_core.html#requireall">&lt;RequireAll&gt;</a></code> et
+ <code class="directive"><a href="../mod/mod_authz_core.html#requireany">&lt;RequireAny&gt;</a></code> permettent d'appliquer une
+ logique telle que l'ordre dans lequel les autorisations sont
+ appliqu矇es peut 礙tre enti癡rement contr繫l矇 au niveau de la
+ configuration. Voir <a href="../mod/mod_authz_core.html#logic">Conteneurs
+ d'autorisations</a> pour un exemple de ce contr繫le.</p>
+
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="beyond" id="beyond">Pour aller plus loin qu'une simple
+autorisation</a></h2>
+
+ <p>La mani癡re dont les autorisations sont accord矇es est d矇sormais
+ beaucoup plus souple qu'une simple v矇rification aupr癡s d'une seule
+ base de donn矇es. Il est maintenant possible de choisir l'ordre, la
+ logique et la mani癡re selon lesquels une autorisation est
+ accord矇e.</p>
+
+ <h3><a name="authandororder" id="authandororder">Appliquer logique et
+ ordonnancement</a></h3>
+ <p>Le contr繫le de la mani癡re et de l'ordre selon lesquels le
+ processus d'autorisation 矇tait appliqu矇
+ constituait une sorte de myst癡re par
+ le pass矇. Dans Apache 2.2, un m矇canisme d'authentification bas矇
+ sur les fournisseurs a 矇t矇 d矇velopp矇 afin de s矇parer le
+ v矇ritable processus d'authentification de l'autorisation et ses
+ diff矇rentes fonctionnalit矇s. Un des avantages colat矇raux
+ r矇sidait dans le fait que les fournisseurs d'authentification
+ pouvaient 礙tre configur矇s et appel矇s selon un ordre particulier
+ ind矇pendant de l'ordre de chargement du module auth proprement
+ dit. Ce m矇canisme bas矇 sur les fournisseurs a 矇t矇 矇tendu au
+ processus d'autorisation. Ceci signifie que la directive
+ <code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code> d矇finit
+ non seulement quelles m矇thodes d'autorisation doivent 礙tre
+ utilis矇es, mais aussi l'ordre dans lequel elles sont appel矇es.
+ Les m矇thodes d'autorisation sont appel矇es selon l'ordre dans
+ lequel les directives <code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code> apparaissent dans la
+ configuration.</p>
+
+ <p>Avec l'introduction des directives de conteneur
+ d'autorisations <code class="directive"><a href="../mod/mod_authz_core.html#requireall">&lt;RequireAll&gt;</a></code>
+ et <code class="directive"><a href="../mod/mod_authz_core.html#requireany">&lt;RequireAny&gt;</a></code>, la
+ configuration contr繫le aussi le moment o羅 les m矇thodes
+ d'autorisation sont appel矇es, et quels crit癡res d矇terminent
+ l'autorisation d'acc癡s. Voir <a href="../mod/mod_authz_core.html#logic">Conteneurs
+ d'autorisations</a> pour un exemple de la mani癡re de les
+ utiliser pour exprimer des logiques d'autorisation
+ complexes.</p>
+
+ <p>Par d矇faut, toutes les directives <code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code> sont
+ trait矇es comme si elles 矇taient contenues dans une directive
+ <code class="directive"><a href="../mod/mod_authz_core.html#requireany">&lt;RequireAny&gt;</a></code>. En d'autres termes, il
+ suffit
+ qu'une m矇thode d'autorisation s'applique avec succ癡s pour que
+ l'autorisation soit accord矇e.</p>
+
+
+
+ <h3><a name="reqaccessctrl" id="reqaccessctrl">Utilisation de fournisseurs
+ d'autorisation pour le contr繫le d'acc癡s</a></h3>
+ <p>La v矇rification du nom d'utilisateur et du mot de passe ne
+ constituent qu'un aspect des m矇thodes d'authentification.
+ Souvent, le contr繫le d'acc癡s certaines personnes n'est pas
+ bas矇 sur leur identit矇 ; il peut d矇pendre, par exemple de leur
+ provenance.</p>
+
+ <p>Les fournisseurs d'autorisation <code>all</code>,
+ <code>env</code>, <code>host</code> et <code>ip</code> vous
+ permettent d'accorder ou refuser l'acc癡s en
+ fonction de crit癡res tels que le nom d'h繫te ou l'adresse
+ IP de la machine qui effectue la requ礙te.</p>
+
+ <p>L'utilisation de ces fournisseurs est sp矇cifi矇e l'aide de
+ la directive <code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code>. Cette directive
+ permet d'enregistrer quels fournisseurs d'autorisation
+ seront appel矇s dans le processus d'autorisation au cours du
+ traitement de la requ礙te. Par exemple :</p>
+
+ <pre class="prettyprint lang-config">Require ip <var>address</var></pre>
+
+
+ <p>o羅 <var>adresse</var> est une adresse IP (ou une adresse IP
+ partielle) ou :</p>
+
+ <pre class="prettyprint lang-config">Require host <var>domain_name</var></pre>
+
+
+ <p>o羅 <var>nom_domaine</var> est un nom de domaine enti癡rement
+ qualif矇 (ou un nom de domaine partiel) ; vous pouvez indiquer
+ plusieurs adresses ou noms de domaines, si vous le d矇sirez.</p>
+
+ <p>Par exemple, si vous voulez rejeter les spams dont une
+ machine vous inonde, vous pouvez utiliser ceci :</p>
+
+ <pre class="prettyprint lang-config">&lt;RequireAll&gt;
+ Require all granted
+ Require not ip 10.252.46.165
+&lt;/RequireAll&gt;</pre>
+
+
+ <p>Ainsi, les visiteurs en provenance de cette adresse ne
+ pourront pas voir le contenu concern矇 par cette directive. Si,
+ par contre, vous connaissez le nom de la machine, vous pouvez
+ utiliser ceci :</p>
+
+ <pre class="prettyprint lang-config">&lt;RequireAll&gt;
+ Require all granted
+ Require not host host.example.com
+&lt;/RequireAll&gt;</pre>
+
+
+ <p>Et si vous voulez interdire l'acc癡s toutes les machines
+ d'un domaine, vous pouvez sp矇cifier une partie seulement de
+ l'adresse ou du nom de domaine :</p>
+
+ <pre class="prettyprint lang-config">&lt;RequireAll&gt;
+ Require all granted
+ Require not ip 192.168.205
+ Require not host phishers.example.com moreidiots.example
+ Require not host ke
+&lt;/RequireAll&gt;</pre>
+
+
+ <p>L'utilisation de la directive <code class="directive"><a href="../mod/mod_authz_core.html#requireall">&lt;RequireAll&gt;</a></code>
+ avec de multiples directives <code class="directive"><a href="../mod/mod_authz_core.html#require">&lt;Require&gt;</a></code>, toutes avec la n矇gation
+ <code>not</code>, n'accordera l'acc癡s que si toutes les
+ conditions n矇gatives sont v矇rifi矇es. En d'autres termes, l'acc癡s
+ sera refus矇 si au moins une des conditions n矇gatives n'est pas
+ v矇rifi矇e.</p>
+
+
+
+ <h3><a name="filesystem" id="filesystem">Compatibilit矇 ascendante du contr繫le
+ d'acc癡s</a></h3>
+ <p>L'adoption d'un m矇canisme base de fournisseurs pour
+ l'authentification, a pour effet colat矇ral de rendre inutiles
+ les directives <code class="directive"><a href="../mod/mod_access_compat.html#order">Order</a></code>, <code class="directive"><a href="../mod/mod_access_compat.html#allow">Allow</a></code>, <code class="directive"><a href="../mod/mod_access_compat.html#deny">Deny</a></code> et <code class="directive"><a href="../mod/mod_access_compat.html#satisfy">Satisfy</a></code>. Cependant, et
+ des fins de compatibilit矇 ascendante vers les anciennes
+ configurations, ces directives ont 矇t矇 d矇plac矇es vers le module
+ <code class="module"><a href="../mod/mod_access_compat.html">mod_access_compat</a></code>.</p>
+
+ <div class="warning"><h3>Note</h3>
+ <p>Les directives fournies par le module
+ <code class="module"><a href="../mod/mod_access_compat.html">mod_access_compat</a></code> sont devenues obsol癡tes depuis
+ la refonte du module <code class="module"><a href="../mod/mod_authz_host.html">mod_authz_host</a></code>. M矇langer d'anciennes
+ directives comme <code class="directive"><a href="../mod/mod_access_compat.html#order">Order</a></code>, <code class="directive"><a href="../mod/mod_access_compat.html#allow">Allow</a></code> ou <code class="directive"><a href="../mod/mod_access_compat.html#deny">Deny</a></code> avec des nouvelles comme
+ <code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code> est techniquement
+ possible mais d矇conseill矇. En effet, <code class="module"><a href="../mod/mod_access_compat.html">mod_access_compat</a></code> a
+ 矇t矇 con癟u pour supporter des configurations ne contenant que des anciennes
+ directives afin de faciliter le passage la version 2.4. Voir le document
+ <a href="../upgrading.html">upgrading</a> pour plus de d矇tails.
+ </p>
+ </div>
+
+
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="socache" id="socache">Mise en cache de l'authentification</a></h2>
+ <p>Dans certains cas, l'authentification constitue une charge
+ inacceptable pour un fournisseur d'authentification ou votre r矇seau.
+ Ceci est susceptible d'affecter les utilisateurs du module
+ <code class="module"><a href="../mod/mod_authn_dbd.html">mod_authn_dbd</a></code> (ou les fournisseurs
+ tiers/personnalis矇s). Pour r矇soudre ce probl癡me, HTTPD 2.3/2.4
+ propose un nouveau fournisseur de mise en cache,
+ <code class="module"><a href="../mod/mod_authn_socache.html">mod_authn_socache</a></code>, qui permet de mettre en cache
+ les donn矇es d'authentification, et ainsi r矇duire la charge du/des
+ fournisseurs(s) originels.</p>
+ <p>Cette mise en cache apportera un gain en performance substantiel
+ certains utilisateurs.</p>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="moreinformation" id="moreinformation">Pour aller plus loin . . .</a></h2>
+ <p>Vous pouvez aussi lire la documentation de
+ <code class="module"><a href="../mod/mod_auth_basic.html">mod_auth_basic</a></code> et <code class="module"><a href="../mod/mod_authz_host.html">mod_authz_host</a></code>
+ qui contient des informations suppl矇mentaires propos du
+ fonctionnement de tout ceci.
+ Certaines configurations d'authentification peuvent aussi 礙tre
+ simplifi矇es l'aide de la directive <code class="directive"><a href="../mod/mod_authn_core.html#authnprovideralias">&lt;AuthnProviderAlias&gt;</a></code>.</p>
+
+ <p>Les diff矇rents algorithmes de chiffrement support矇s par Apache
+ pour authentifier les donn矇es sont expliqu矇s dans <a href="../misc/password_encryptions.html">PasswordEncryptions</a>.</p>
+
+ <p>Enfin vous pouvez consulter la recette <a href="access.html">Contr繫le
+ d'acc癡s</a>, qui d矇crit un certain nombre de situations en relation
+ avec le sujet.</p>
+
+</div></div>
+<div class="bottomlang">
+<p><span>Langues Disponibles: </span><a href="../en/howto/auth.html" hreflang="en" rel="alternate" title="English">&nbsp;en&nbsp;</a> |
+<a href="../es/howto/auth.html" hreflang="es" rel="alternate" title="Espa簽ol">&nbsp;es&nbsp;</a> |
+<a href="../fr/howto/auth.html" title="Fran癟ais">&nbsp;fr&nbsp;</a> |
+<a href="../ja/howto/auth.html" hreflang="ja" rel="alternate" title="Japanese">&nbsp;ja&nbsp;</a> |
+<a href="../ko/howto/auth.html" hreflang="ko" rel="alternate" title="Korean">&nbsp;ko&nbsp;</a> |
+<a href="../tr/howto/auth.html" hreflang="tr" rel="alternate" title="T羹rk癟e">&nbsp;tr&nbsp;</a></p>
+</div><div class="top"><a href="#page-header"><img src="../images/up.gif" alt="top" /></a></div><div class="section"><h2><a id="comments_section" name="comments_section">Commentaires</a></h2><div class="warning"><strong>Notice:</strong><br />This is not a Q&amp;A section. Comments placed here should be pointed towards suggestions on improving the documentation or server, and may be removed by our moderators if they are either implemented or considered invalid/off-topic. Questions on how to manage the Apache HTTP Server should be directed at either our IRC channel, #httpd, on Libera.chat, or sent to our <a href="https://httpd.apache.org/lists.html">mailing lists</a>.</div>
+<script type="text/javascript"><!--//--><![CDATA[//><!--
+var comments_shortname = 'httpd';
+var comments_identifier = 'http://httpd.apache.org/docs/2.4/howto/auth.html';
+(function(w, d) {
+ if (w.location.hostname.toLowerCase() == "httpd.apache.org") {
+ d.write('<div id="comments_thread"><\/div>');
+ var s = d.createElement('script');
+ s.type = 'text/javascript';
+ s.async = true;
+ s.src = 'https://comments.apache.org/show_comments.lua?site=' + comments_shortname + '&page=' + comments_identifier;
+ (d.getElementsByTagName('head')[0] || d.getElementsByTagName('body')[0]).appendChild(s);
+ }
+ else {
+ d.write('<div id="comments_thread">Comments are disabled for this page at the moment.<\/div>');
+ }
+})(window, document);
+//--><!]]></script></div><div id="footer">
+<p class="apache">Copyright 2023 The Apache Software Foundation.<br />Autoris矇 sous <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p>
+<p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a> | <a href="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="../glossary.html">Glossaire</a> | <a href="../sitemap.html">Plan du site</a></p></div><script type="text/javascript"><!--//--><![CDATA[//><!--
+if (typeof(prettyPrint) !== 'undefined') {
+ prettyPrint();
+}
+//--><!]]></script>
+</body></html> \ No newline at end of file
diff --git a/docs/manual/howto/auth.html.ja.utf8 b/docs/manual/howto/auth.html.ja.utf8
new file mode 100644
index 0000000..78519bd
--- /dev/null
+++ b/docs/manual/howto/auth.html.ja.utf8
@@ -0,0 +1,692 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="ja" xml:lang="ja"><head>
+<meta content="text/html; charset=UTF-8" http-equiv="Content-Type" />
+<!--
+ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+ This file is generated from xml source: DO NOT EDIT
+ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+ -->
+<title>隤閮潦輯U胯颯孵嗅鴃 - Apache HTTP 萸潦 潦詻扼 2.4</title>
+<link href="../style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" />
+<link href="../style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" />
+<link href="../style/css/manual-print.css" rel="stylesheet" media="print" type="text/css" /><link rel="stylesheet" type="text/css" href="../style/css/prettify.css" />
+<script src="../style/scripts/prettify.min.js" type="text/javascript">
+</script>
+
+<link href="../images/favicon.ico" rel="shortcut icon" /></head>
+<body id="manual-page"><div id="page-header">
+<p class="menu"><a href="../mod/">U詻乓潦</a> | <a href="../mod/directives.html">研胯</a> | <a href="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="../glossary.html">刻</a> | <a href="../sitemap.html">萸扎</a></p>
+<p class="apache">Apache HTTP 萸潦 潦詻扼 2.4</p>
+<img alt="" src="../images/feather.png" /></div>
+<div class="up"><a href="./"><img title="&lt;-" alt="&lt;-" src="../images/left.gif" /></a></div>
+<div id="path">
+<a href="http://www.apache.org/">Apache</a> &gt; <a href="http://httpd.apache.org/">HTTP 萸潦</a> &gt; <a href="http://httpd.apache.org/docs/">准乓∼喋潦瑯扼</a> &gt; <a href="../">潦詻扼 2.4</a> &gt; <a href="./">How-To / 乓潦芥U</a></div><div id="page-content"><div id="preamble"><h1>隤閮潦輯U胯颯孵嗅鴃</h1>
+<div class="toplang">
+<p><span>蝧餉迅皜輯隤: </span><a href="../en/howto/auth.html" hreflang="en" rel="alternate" title="English">&nbsp;en&nbsp;</a> |
+<a href="../es/howto/auth.html" hreflang="es" rel="alternate" title="Espa簽ol">&nbsp;es&nbsp;</a> |
+<a href="../fr/howto/auth.html" hreflang="fr" rel="alternate" title="Fran癟ais">&nbsp;fr&nbsp;</a> |
+<a href="../ja/howto/auth.html" title="Japanese">&nbsp;ja&nbsp;</a> |
+<a href="../ko/howto/auth.html" hreflang="ko" rel="alternate" title="Korean">&nbsp;ko&nbsp;</a> |
+<a href="../tr/howto/auth.html" hreflang="tr" rel="alternate" title="T羹rk癟e">&nbsp;tr&nbsp;</a></p>
+</div>
+<div class="outofdate">格交祈閮喋胯扼怠扎芥艾
+ 航賣扼整
+ 餈湔啜摰嫘閬怒航梯閬找
+ </div>
+
+ <p>隤閮潦具胯隤啜芸航狐扼銝餃撐游怒
+ 蝣箄桀券蝔整輯具胯
+ 隤啜銵湔怨怒舀炬晞
+ 敺具扼怒桀券蝔整</p>
+</div>
+<div id="quickview"><a href="https://www.apache.org/foundation/contributing.html" class="badge"><img src="https://www.apache.org/images/SupportApache-small.png" alt="Support Apache!" /></a><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#related">aU詻乓潦怒具研胯</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#introduction">胯</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#theprerequisites">皞</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#gettingitworking">雿</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#lettingmorethanonepersonin">
+銴啜桐犖乓怒</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#possibleproblems">韏瑯憿</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#dbmdbd">嫘胯潦桐摮敶W憭</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#multprovider">銴啜柴准扎雿輻具</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#beyond">蝝芣輯柴桀</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#moreinformation">餈賢</a></li>
+</ul><h3></h3><ul class="seealso"><li><a href="#comments_section">喋∼喋</a></li></ul></div>
+<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="related" id="related">aU詻乓潦怒具研胯</a></h2>
+<p>隤閮潦冽輯桀衣恍a 3 蝔桅柴U詻乓潦怒整
+撠芥具脯具扎文閬扼</p>
+
+<ul>
+ <li>隤閮潦柴踴扎 (
+ <code class="directive"><a href="../mod/core.html#authtype">AuthType</a></code> 研胯)
+ <ul>
+ <li><code class="module"><a href="../mod/mod_auth_basic.html">mod_auth_basic</a></code></li>
+ <li><code class="module"><a href="../mod/mod_auth_digest.html">mod_auth_digest</a></code></li>
+ </ul>
+ </li>
+ <li>隤閮潦准扎 (
+ <code class="directive"><a href="../mod/mod_auth_basic.html#authbasicprovider">AuthBasicProvider</a></code>,
+ <code class="directive"><a href="../mod/mod_auth_digest.html#authdigestprovider">AuthDigestProvider</a></code> 研胯)
+
+ <ul>
+ <li><code class="module"><a href="../mod/mod_authn_anon.html">mod_authn_anon</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authn_dbd.html">mod_authn_dbd</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authn_dbm.html">mod_authn_dbm</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authn_default.html">mod_authn_default</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authn_file.html">mod_authn_file</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authnz_ldap.html">mod_authnz_ldap</a></code></li>
+ </ul>
+ </li>
+ <li>輯 (
+ <code class="directive"><a href="../mod/core.html#require">Require</a></code> 研胯)
+ <ul>
+ <li><code class="module"><a href="../mod/mod_authnz_ldap.html">mod_authnz_ldap</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authz_dbm.html">mod_authz_dbm</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authz_dbm.html">mod_authz_dbm</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authz_default.html">mod_authz_default</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authz_groupfile.html">mod_authz_groupfile</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authz_host.html">mod_authz_host</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authz_owner.html">mod_authz_owner</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authz_user.html">mod_authz_user</a></code></li>
+ </ul>
+ </li>
+</ul>
+
+ <p>柴U詻乓潦怒怠艾<code class="module"><a href="../mod/mod_authn_core.html">mod_authn_core</a></code>
+ <code class="module"><a href="../mod/mod_authz_core.html">mod_authz_core</a></code> 整
+ 2 扎柴U詻乓潦怒航閮潦U詻乓潦怒怠梢芥喋U研胯
+ 摰鋆艾整</p>
+
+ <p><code class="module"><a href="../mod/mod_authnz_ldap.html">mod_authnz_ldap</a></code> 航閮潦准扎冽輯准扎
+ 銝⊥嫘格賬艾整
+ <code class="module"><a href="../mod/mod_authz_host.html">mod_authz_host</a></code> 胯嫘IP U研嫘
+ 芥胯具嫘桃孵噹怠箝乓U胯颯孵嗅鴃銵整
+ 隤閮潦准扎柴瑯嫘桐具扼胯整
+ mod_access 具桀嫣扼柴
+ 啜U詻乓潦怒 <code class="module"><a href="../mod/mod_access_compat.html">mod_access_compat</a></code> 整</p>
+
+ <p>瑽芥U胯颯孵嗅鴃株芥嫘怒扎艾胯
+ <a href="access.html">U胯颯孵嗅鴃</a>格寞閬扼</p>
+
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="introduction" id="introduction">胯</a></h2>
+ <p>璈撖格晞撠啜啜怒潦桐犖格晞
+ 艾扼萸扎怎蔭柴扼啜格詻急詻艾
+ 胯胯雿踴具扼柴潦詻閬艾鈭箝∼
+ 踴桐犖∼扼具蝣箏怒扼扼</p>
+
+ <p>格詻扼胯憭桐犖∠具扼
+ 艾扼萸扎桐典靽霅瑯銝祉芥
+ 寞怒扎艾怒潦艾整</p>
+
+ <div class="note"><h3>瘜冽</h3>
+ <p>潦踴砍急撖芥柴扼啜隤閮潦怠艾
+ <code class="module"><a href="../mod/mod_ssl.html">mod_ssl</a></code> 雿踴刻胯扼</p>
+ </div>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="theprerequisites" id="theprerequisites">皞</a></h2>
+ <p>格詻批晞研胯胯
+ ∼扎喋萸潦閮剖∼扎 (桅
+ <code class="directive"><a href="../mod/core.html#directory">&lt;Directory&gt;</a></code>
+ 颯胯瑯扼喃葉) 胯研胯芣株身摰∼扎
+ (<code>.htaccess</code> ∼扎) 抒具整</p>
+
+ <p><code>.htaccess</code> ∼扎怒具柴扼啜
+ 柴∼扎怒怨閮潛具柴研胯蝵柴
+ 萸潦株身摰芥具芥扼
+ <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code>
+ 研胯批航賬怒芥整
+ <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code>
+ 研胯扼胯研胯芣株身摰∼扎思葉怎蔭具柴扼
+ 研胯啜摰整</p>
+
+ <p>隤閮潦怒扎西店脯艾柴扼甈∼柴
+ <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code>
+ 研胯敹閬怒芥扼</p>
+
+ <div class="example"><p><code>
+ AllowOverride AuthConfig
+ </code></p></div>
+
+ <p>扼芥∼扎喋萸潦閮剖∼扎怒桐葉
+ 湔亦蔭柴扼啜敶嗚芥柴∼扎怒詻格詻颲潦
+ 璅拚艾芥啜芥芥扼</p>
+
+ <p>整押柴∼扎怒押思摮艾乓怒
+ 萸潦柴研胯芣怒扎血乓艾
+ 敹閬扼
+ 胯芥恍芥柴扼格訾葉
+ 研胯芣怒扎衣乓艾敹閬湧U扼胯
+ 怒芥怒整</p>
+
+ <p><code class="module"><a href="../mod/mod_authn_core.html">mod_authn_core</a></code> <code class="module"><a href="../mod/mod_authz_core.html">mod_authz_core</a></code>
+ 桐腹嫘 httpd 扎芥恍怎輯噯踵踴扼httpd.conf
+ 閮剖∼扎怒批怒准潦艾httpd 怎輯噯整艾芥
+ 芥整桐扎柴U詻乓潦怒胯閮剖∼扎怒柴芥折撣詻
+ 閬扼艾扼萸潦株閮潦冽輯找蝙具喋U研胯
+ 格賬靘艾整</p>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="gettingitworking" id="gettingitworking">雿</a></h2>
+ <p>扼胯萸潦銝柴研胯芥嫘胯潦找霅瑯
+ 箸祆蝷箝整</p>
+
+ <p>整胯怒嫘胯潦∼扎怒雿整
+ 押株閮潦准扎雿踴怒艾嫘胯潦∼扎怎格
+ 憭扼啜芥整扼桐扼胯憪怒准嫘嫘胯潦∼扎怒
+ 雿踴整</p>
+
+ <p>柴嫘胯潦∼扎怒胯艾扼U胯颯嫘扼湔
+ 蝵柴嫘扼胯整隞桐犖嫘胯潦∼扎怒
+ 艾喋准潦扼芥怒扼靘啜
+ <code>/usr/local/apache/htdocs</code> 扼准乓∼喋
+ 靘艾柴扼啜嫘胯潦∼扎怒
+ <code>/usr/local/apache/passwd</code>
+ 芥押怎蔭嫘胯扼</p>
+
+ <p>∼扎怒雿怒胯Apache 隞撅 <code class="program"><a href="../programs/htpasswd.html">htpasswd</a></code>
+ 雿踴整柴喋喋 Apache 押怒扎喋嫘潦怒具
+ 扎喋嫘潦怒研胯芥 <code>bin</code>
+ 研胯芯誑銝怎蔭整萸潦潦鋆賬柴晞潦詻
+ 扎喋嫘潦怒游胯摰銵嫘桐葉扯扎扼</p>
+
+ <p>∼扎怒雿怒胯甈∼柴怒踴扎艾</p>
+
+ <div class="example"><p><code>
+ htpasswd -c /usr/local/apache/passwd/passwords rbowen
+ </code></p></div>
+
+ <p><code class="program"><a href="../programs/htpasswd.html">htpasswd</a></code> 胯嫘胯潦閬瘙桀
+ 蝣箄柴怒銝摨血亙怨瘙艾整</p>
+
+ <div class="example"><p><code>
+ # htpasswd -c /usr/local/apache/passwd/passwords rbowen<br />
+ New password: mypassword<br />
+ Re-type new password: mypassword<br />
+ Adding password for user rbowen
+ </code></p></div>
+
+ <p> <code class="program"><a href="../programs/htpasswd.html">htpasswd</a></code> 嫘桐葉怠乓艾芥游胯
+ ∼摰銵怒准啜押整扼柴怒嫘
+ 踴扎敹閬整押怒柴扎喋嫘潦怎嗆扼啜
+ <code>/usr/local/apache/bin/htpasswd</code>
+ 怒准啜押蝵柴艾整</p>
+
+ <p>甈∼怒萸潦嫘胯潦閬瘙怨身摰艾
+ 押柴艾潦嗚U胯颯嫘閮晞艾萸潦怎乓芥
+ 芥整 <code>httpd.conf</code> 蝺券
+ <code>.htaccess</code> ∼扎怒雿輻具
+ 閮剖整靘啜研胯
+ <code>/usr/local/apache/htdocs/secret</code>
+ 靽霅瑯游胯
+ <code>/usr/local/apache/htdocs/secret/.htaccess</code>
+ httpd.conf 銝准 &lt;Directory
+ /usr/local/apache/htdocs/secret&gt; 颯胯瑯扼喋
+ 蝵柴艾甈∼柴研胯雿踴具扼整</p>
+
+ <div class="example"><p><code>
+ AuthType Basic<br />
+ AuthName "Restricted Files"<br />
+ # (Following line optional)<br />
+ AuthBasicProvider file<br />
+ AuthUserFile /usr/local/apache/passwd/passwords<br />
+ Require user rbowen
+ </code></p></div>
+
+ <p>柴研胯怒扎西艾踴整
+ <code class="directive"><a href="../mod/core.html#authtype">AuthType</a></code>
+ 研胯胯押隤閮潭寞扼艾潦嗚株閮潦銵
+ 豢整銝祉芣寞 <code>Basic</code>
+ 扼 <code class="module"><a href="../mod/mod_auth_basic.html">mod_auth_basic</a></code>
+ 批鋆艾整芥
+ 舀隞嫘閬芥扎喋芥柴扼
+ Basic 隤閮潦胯胯押扎U喋萸潦詻
+ 嫘胯潦瑕恍整扼格寞胯
+ <code class="module"><a href="../mod/mod_ssl.html">mod_ssl</a></code> 函踹芥嗆扼胯
+ 嫘急撖扼桅潦踴怠紋艾舐具嫘扼
+ 整 Apache 扼胯銝文乓株閮潭寞:
+ <code>AuthType Digest</code> 萸潦艾整
+ 格寞 <code class="module"><a href="../mod/mod_auth_digest.html">mod_auth_digest</a></code>
+ 批鋆艾艾典具扼
+ 餈柴胯押扎U喋 Digest
+ 隤閮潦萸潦艾扼</p>
+
+ <p><code class="directive"><a href="../mod/core.html#authname">AuthName</a></code>
+ 研胯扼胯隤閮潦思蝙 <dfn>Realm</dfn> (閮單釣: )
+ 閮剖整Realm 臬之虫扎格賬靘整
+ 銝斤柴胯胯押扎U喋嫘胯潦扎U准啜胯嫘
+ 銝具具艾艾潦嗚怒格晞蝷箝具柴扼
+ 鈭斤柴怒胯胯押扎U喋銝隤閮潮怠紋艾押柴嫘胯潦
+ 靽∼啗胯柴瘙箏思蝙具璈賬扼</p>
+
+ <p>靘啜<code>"Restricted Files"</code> 銝准
+ 銝摨西閮潦啜銝萸潦銝 <code>"Restricted Files"</code>
+ Realm 具艾潦胯押芷扼胯押扎U喋
+ 芸怠嫘胯潦雿踴刻岫踴整
+ 柴扼銴啜桀園怠 realm 望艾
+ 艾潦嗚嫘胯潦雿摨艾閬瘙鈭
+ 脯具扼整∼颯准乓芥銝桃晞
+ 萸潦柴嫘憭啜扎扼敹
+ 胯押扎U喋臬喋嫘胯潦撠准敹閬整</p>
+
+ <p><code class="directive"><a href="../mod/mod_auth_basic.html#authbasicprovider">AuthBasicProvider</a></code>
+ 胯押怒扎 <code>file</code> 芥柴扼隞桀游舐∼艾瑽整
+ <code class="module"><a href="../mod/mod_authn_dbm.html">mod_authn_dbm</a></code> <code class="module"><a href="../mod/mod_authn_dbd.html">mod_authn_dbd</a></code>
+ 具隞柴U詻乓潦怒雿踴游怒臬閬怒芥整
+ </p>
+
+ <p><code class="directive"><a href="../mod/mod_authn_file.html#authuserfile">AuthUserFile</a></code>
+ 研胯 <code class="program"><a href="../programs/htpasswd.html">htpasswd</a></code> 找
+ 嫘胯潦∼扎怒詻柴嫘閮剖整
+ 艾潦嗆啜憭游胯芥胯具嫘瘥柴艾潦嗚株閮潦柴
+ 研潦喋准嫘格Y揣撣詻恍芥具整
+ Apache 扼胯艾潦嗆晞擃芥潦踴潦嫘∼扎怒
+ 靽蝞∼具扼整
+ <code class="module"><a href="../mod/mod_authn_dbm.html">mod_authn_dbm</a></code> U詻乓潦怒
+ <code class="directive"><a href="../mod/mod_authn_dbm.html#authdbmuserfile">AuthDBMUserFile</a></code>
+ 研胯靘整柴∼扎怒 <code class="program"><a href="../programs/dbmmanage.html">dbmmanage</a></code>
+ 准啜押找雿扼整
+ <a href="http://modules.apache.org/">Apache
+ U詻乓潦怒潦踴潦</a>銝准怒萸潦潦潸ˊ
+ U詻乓潦怒扼桐憭柴踴扎株閮潦芥瑯扼喋
+ 拍典航賬扼</p>
+
+ <p>敺怒<code class="directive"><a href="../mod/core.html#require">Require</a></code>
+ 研胯萸潦柴桅怒U胯颯嫘扼艾潦嗚
+ 摰具怒艾准颯嫘格輯典靘整
+ 甈∼柴颯胯瑯扼喋扼胯<code class="directive"><a href="../mod/core.html#require">Require</a></code>
+ 研胯格芰冽怒扎西膩嫘整</p>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="lettingmorethanonepersonin" id="lettingmorethanonepersonin">
+銴啜桐犖乓怒</a></h2>
+ <p>銝閮柴研胯胯銝鈭 (瑚怒胯艾潦嗅
+ <code>rbowen</code> 株狐) 研胯芥
+ 乓怒整憭桀游胯銴啜桐犖
+ 乓怒扼
+ <code class="directive"><a href="../mod/mod_authz_groupfile.html#authgroupfile">AuthGroupFile</a></code>
+ 桃餃氬扼</p>
+
+ <p>銴啜桐犖乓怒柴扼啜
+ 啜怒潦怠艾潦嗚桐閬扼桀乓艾啜怒潦柴扎
+ 啜怒潦∼扎怒雿敹閬整柴∼扎怒
+ 詨胯血蝝扼憟賬踴柴具踴抒扼整
+ ∼扎怒桐葉頨怒舀活柴芥柴扼</p>
+
+ <div class="example"><p><code>
+ GroupName: rbowen dpitts sungo rshersey
+ </code></p></div>
+
+ <p>銝銵怒嫘潦孵箏扼啜怒潦急撅∼喋潦
+ 銝閬扼芥嫘扼</p>
+
+ <p>U怠具嫘胯潦∼扎怒怒艾潦嗚游胯
+ 甈∼柴怒踴扎艾</p>
+
+ <div class="example"><p><code>
+ htpasswd /usr/local/apache/passwd/passwords dpitts
+ </code></p></div>
+
+ <p>隞亙典敹蝑餈整啜∼扎怒
+ 雿柴扼胯芥U怒∼扎怒怨蕭艾整
+ (啜嫘胯潦∼扎怒雿怒 <code>-c</code>
+ 雿踴整)</p>
+
+ <p>扳活柴怒 <code>.htaccess</code> ∼扎怒
+ 靽格迤敹閬整</p>
+
+ <div class="example"><p><code>
+ AuthType Basic<br />
+ AuthName "By Invitation Only"<br />
+ # Optional line:<br />
+ AuthBasicProvider file<br />
+ AuthUserFile /usr/local/apache/passwd/passwords<br />
+ AuthGroupFile /usr/local/apache/passwd/groups<br />
+ Require group GroupName
+ </code></p></div>
+
+ <p>扼啜怒潦 <code>GroupName</code> 怒芥嫘艾艾
+ <code>password</code> ∼扎怒怒具喋芥鈭箝胯
+ 甇嫘胯潦踴扎啣乓具扼扼</p>
+
+ <p>函孵怨啜柴艾潦嗚乓怒
+ 銝扎格寞整啜怒潦∼扎怒雿柴扼胯芥
+ 甈∼柴研胯雿踴啜扼整</p>
+
+ <div class="example"><p><code>
+ Require valid-user
+ </code></p></div>
+
+ <p><code>require user rbowen</code> 銵扼芥銝閮雿踴具
+ 嫘胯潦∼扎怒怒芥嫘艾鈭箝扼啗狐扼
+ 閮勗胯整
+ 怒嫘胯潦∼扎怒啜怒潦瘥怠艾具扼
+ 啜怒潦柴芣胯具扼整
+ 柴U准潦桀拍嫘胯Apache 臭扎扼胯芥
+ 銝扎柴∼扎怒璊颯啜具嫘扼
+ 甈嫘胯柴嫘胯潦∼扎怒蝞∠艾桐葉
+ <code class="directive"><a href="../mod/mod_authn_file.html#authuserfile">AuthUserFile</a></code>
+ 研胯急迤∼扎怒扼芥啜芥芥嫘扼</p>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="possibleproblems" id="possibleproblems">韏瑯憿</a></h2>
+ <p>Basic 隤閮潦摰艾游胯
+ 萸潦怒准乓∼喋芥胯具嫘摨艾
+ 艾潦嗅具嫘胯潦璊颯芥啜芥整
+ 臬潦詻潦詻怒具艾桃餃
+ 芥准潦游扼艾閰脣整
+ (餃靽霅瑯研胯芥乓柴扼)
+ 鈭喋臬雿憭撠整
+ 芥蝔摨艾胯嫘胯潦∼扎怒桀之冽靘整
+ 胯∼扎怒艾芥桀箄整
+ 艾潦嗅柴芥嫘隤准整芥啜芥芥扼
+ 艾潦詻准潦摨艾怒銵芥
+ 芥整</p>
+
+ <p>蝯隢具艾胯銝扎柴嫘胯潦∼扎怒怎蔭具柴扼
+ 艾潦嗆啜怒臬鞈芰芷整
+ 桅胯萸潦瑯喋格扯賬思摮血整
+ 啁整柴具喋芥頞摨虫銝閬其艾整
+ 格臭株閮潭寞柴怠乓嫘胯扼</p>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="dbmdbd" id="dbmdbd">嫘胯潦桐摮敶W憭</a></h2>
+
+ <p>研潦喋准嫘扼嫘胯潦靽摮寞怒臭閮桀憿
+ 潦踴潦嫘柴芸乓桀湔怒嫘胯潦靽摮冽
+ 整</p>
+
+ <p><code class="module"><a href="../mod/mod_authn_dbm.html">mod_authn_dbm</a></code> <code class="module"><a href="../mod/mod_authn_dbd.html">mod_authn_dbd</a></code>
+ 雿踴具扼怒芥整
+ <code class="directive"><a href="../mod/mod_auth_basic.html#authbasicsource">AuthBasicSource</a></code>
+ file 桐誨怒<code>dbm</code> <code>dbd</code>
+ 潛敶W具阡詻嫘整</p>
+
+ <p>准嫘∼扎怒桐誨 dbm ∼扎怒豢游胯具唳活柴怒整</p>
+
+ <div class="example"><p><code>
+ &lt;Directory /www/docs/private&gt;<br />
+ AuthName "Private"<br />
+ AuthType Basic<br />
+ AuthBasicProvider dbm<br />
+ AuthDBMUserFile /www/passwords/passwd.dbm<br />
+ Require valid-user<br />
+ &lt;/Directory&gt;
+ </code></p></div>
+
+ <p>桐柴芥瑯扼喋摮具整閰喟敦恍U艾
+ <code class="module"><a href="../mod/mod_authn_dbm.html">mod_authn_dbm</a></code> 柴准乓∼喋閬扼</p>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="multprovider" id="multprovider">銴啜柴准扎雿輻具</a></h2>
+
+ <p>隤閮潭輯U潦准胯怠箝乓艾啜准扎雿踴具
+ 隤閮潭輯格寞脯具扎怎敹閬芥芥整
+ 扎柴准扎蝯踹艾芸格踴格怒扼整
+ 甈∼桐扼 file 隤閮潦准扎 ldap 隤閮潦准扎
+ 蝯踹艾整</p>
+
+ <div class="example"><p><code>
+ &lt;Directory /www/docs/private&gt;<br />
+ AuthName "Private"<br />
+ AuthType Basic<br />
+ AuthBasicProvider file ldap<br />
+ AuthUserFile /usr/local/apache/passwd/passwords<br />
+ AuthLDAPURL ldap://ldaphost/o=yourorg<br />
+ Require valid-user
+ </code></p></div>
+
+ <p>桐扼胯整 file 准扎艾潦嗉閮潦閰艾踴整
+ 隤閮潦扼芥游怒胯ldap 准扎潦喳箝整
+ 蝯蝜扯啜株閮潭潛寞雿踴艾芥押怒
+ 格寞雿踴西閮潦柴嫘喋潦∪之扼整
+ 脯具扎柴瑯芥芥胯脯具扎株閮潦踴扎函啜芥輯
+ 蝯踹寞扼具啜嫘胯潦∼扎怒扯閮潦艾
+ ldap 研胯芥扳輯銵具游扼</p>
+
+ <p>隤閮潦准扎銴啣鋆扼怒輯寞銴唬蝙具扼整
+ 桐扼 file 啜怒潦輯 ldap 啜怒潦輯雿踴艾整</p>
+
+ <div class="example"><p><code>
+ &lt;Directory /www/docs/private&gt;<br />
+ AuthName "Private"<br />
+ AuthType Basic<br />
+ AuthBasicProvider file<br />
+ AuthUserFile /usr/local/apache/passwd/passwords<br />
+ AuthLDAPURL ldap://ldaphost/o=yourorg
+ AuthGroupFile /usr/local/apache/passwd/groups<br />
+ Require group GroupName<br />
+ Require ldap-group cn=mygroup,o=yourorg
+ </code></p></div>
+
+ <p>輯蝝啜嗅鴃游胯
+ <code class="directive"><a href="../mod/mod_authz_core.html#&lt;satisfyall&gt;">&lt;SatisfyAll&gt;</a></code>
+ <code class="directive"><a href="../mod/mod_authz_core.html#&lt;satisfyone&gt;">&lt;SatisfyOne&gt;</a></code>
+ 研胯雿踴 AND/OR 准詻胯扳摰閮剖∼扎怒
+ 輯桀衣芥桀嗅鴃扼怒芥艾整
+ 柴研胯押柴思蝙蝬脩靘閬扼</p>
+
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="beyond" id="beyond">蝝芣輯柴桀</a></h2>
+
+ <p>輯格寞胯脯具扎柴潦踴賬潦嫘閬虫扼胯柴冽嫘艾
+ 典敶押芷拍冽寞扼整
+ 輯衣桅拍券摨嗅鴃豢扼怒芥整</p>
+
+ <h3><a name="authandororder" id="authandororder">AND/OR 准詻胯桅拍具券摨隞</a></h3>
+ <p>輯押柴芷摨折拍具艾整押柴怠嗅鴃胯
+ 整扳毽銋晞艾整
+ Apache 2.2 扼胯准扎潦嫘株閮潦∼怒箝撠乓
+ 輯衣隤閮澆衣具萸潦璈賬具整
+ 怒脯具扎桀寞具艾
+ 隤閮潦U詻乓潦怒柴准潦U詻乓潦怨芯桅摨思摮具芥
+ 摰芥扯閮潦准扎潦喳箝
+ 閮剖扼怒芥整
+ 柴准扎∼怒箝舀輯衣扼撠乓艾整
+ 扎整<code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code>
+ 研胯臬怒押格輯瘜雿踴摰扼胯芥
+ 桀潦喳箝摨摰扼怒芥整
+ 銴啜格輯瘜具桀潦喳箝胯閮剖∼扎怒
+ <code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code> 研胯銝准
+ 整摨典怒芥整</p>
+
+ <p>餈賢批乓
+ <code class="directive"><a href="../mod/mod_authz_core.html#&lt;satisfyall&gt;">&lt;SatisfyAll&gt;</a></code>,
+ <code class="directive"><a href="../mod/mod_authz_core.html#&lt;satisfyone&gt;">&lt;SatisfyOne&gt;</a></code>
+ 研胯雿踴艾輯瘜文潦喳箝U胯颯嫘閮勗胯
+ 押格蝬拍具摰具扼整
+ 具啜甈∼格輯准胯柴准詻胯閬艾踴整:</p>
+
+ <div class="example"><p><code>
+ # if ((user == "John") ||<br />
+ # &nbsp;&nbsp; ((Group == "admin")<br />
+ # &nbsp; &nbsp; &amp;&amp; (ldap-group &lt;ldap-object&gt; contains auth'ed_user)<br />
+ # &nbsp; &nbsp; &amp;&amp; ((ldap-attribute dept == "sales")<br />
+ # &nbsp; &nbsp; &nbsp; &nbsp; || (file-group contains auth'ed_user))))<br />
+ # then<br />
+ # &nbsp; auth_granted<br />
+ # else<br />
+ # &nbsp; auth_denied<br />
+ #<br />
+ &lt;Directory /www/mydocs&gt;<br />
+ <span class="indent">
+ Authname ...<br />
+ AuthBasicProvider ...<br />
+ ...<br />
+ Require user John<br />
+ &lt;SatisfyAll&gt;<br />
+ <span class="indent">
+ Require Group admins<br />
+ Require ldap-group cn=mygroup,o=foo<br />
+ &lt;SatisfyOne&gt;<br />
+ <span class="indent">
+ Require ldap-attribute dept="sales"<br />
+ Require file-group<br />
+ </span>
+ &lt;/SatisfyOne&gt;<br />
+ </span>
+ &lt;/SatisfyAll&gt;<br />
+ </span>
+ &lt;/Directory&gt;
+ </code></p></div>
+
+ <p>押怒扼 <code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code>
+ 研胯 OR 雿具行晞整扎整摰輯瘜
+ 脯具扎扼潦啜輯整
+ <code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code> 研胯柴颯
+ 脯具扎 <code class="directive"><a href="../mod/mod_authz_core.html#&lt;satisfyall&gt;">&lt;SatisfyAll&gt;</a></code>
+ 准胯批脯杗ND 雿具芥具艾格輯瘜批潦芥啗迂胯整</p>
+
+
+
+ <h3><a name="reqaccessctrl" id="reqaccessctrl">U胯颯孵嗅鴃怒 Require Reject 桐蝙</a></h3>
+ <p>艾潦嗅具嫘胯潦怒隤閮潦臬其桐典扼整
+ 隤啜U胯颯嫘艾具曹誑憭格∩辣雿踴
+ 具具扼
+ 具啜押U胯颯嫘艾艾具瑕扼</p>
+
+ <p>輯准扎 <code class="directive"><a href="../mod/mod_authz_host.html#all">all</a></code>,
+ <code class="directive"><a href="../mod/mod_authz_host.html#env">env</a></code>,
+ <code class="directive"><a href="../mod/mod_authz_host.html#host">host</a></code>,
+ <code class="directive"><a href="../mod/mod_authz_host.html#ip">ip</a></code>
+ 雿踴具芥胯具嫘靽∼艾艾瑯喋柴嫘 IP U研
+ 具嫘潦嫘扼柴U胯颯孵嗅鴃扼整</p>
+
+ <p>准扎格晞
+ <code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code>
+ <code class="directive"><a href="../mod/mod_authz_core.html#reject">Reject</a></code>
+ 摰整柴研胯舀輯准扎駁脯
+ 芥胯具嫘衣格輯畾菟批潦喳箝整具:</p>
+
+ <div class="example"><p><code>
+ Require ip <var>address</var>
+ </code></p></div>
+
+ <p>扼<var>address</var> IP U研 ( IP U研嫘
+ 銝) : </p>
+
+ <div class="example"><p><code>
+ Require host <var>domain_name</var>
+ </code></p></div>
+
+ <p> <var>domain_name</var> FQDN (胯∼扎喳桐)
+ 扼敹閬扼啗啜柴U研嫘∼扎喳詻具扼整</p>
+
+ <p>具啜嫘∼颯潦詻靽∼艾隤啜艾游
+ 甈∼柴怒芥整 : </p>
+
+ <div class="example"><p><code>
+ Reject ip 10.252.46.165
+ </code></p></div>
+
+ <p>柴研胯嫘芰脯柴喋喋喋怠紋艾胯
+ 柴U研嫘U胯颯嫘艾艾閬具扼整
+ 瑯喳艾 IP U研嫘∼
+ 摰柴扼啜柴瑯喳雿踴整</p>
+
+ <div class="example"><p><code>
+ Reject host <var>host.example.com</var>
+ </code></p></div>
+
+ <p>整孵柴∼扎喋柴U胯颯孵具艾准胯游胯
+ IP U研嫘桐具∼扎喳摰扼整 :</p>
+
+ <div class="example"><p><code>
+ &lt;SatisfyAll&gt;<br />
+ <span class="indent">
+ Reject ip <var>192.168.205</var><br />
+ Reject host <var>phishers.example.com</var> <var>moreidiots.example</var><br /> Reject host ke<br />
+ </span>
+ &lt;/SatisfyAll&gt;
+ </code></p></div>
+
+ <p><code class="directive"><a href="../mod/mod_authz_host.html#reject">Reject</a></code> 研胯
+ <code class="directive"><a href="../mod/mod_authz_core.html#&lt;satisfyall&gt;">&lt;SatisfyAll&gt;</a></code> 准胯桐葉找蝙具
+ 閮勗胯啜怒潦怒柴踴U胯颯嫘扼怎Ⅱ隤扼整</p>
+
+ <p>銝閮桐扼 <code class="directive"><a href="../mod/mod_authz_core.html#&lt;satisfyall&gt;">&lt;SatisfyAll&gt;</a></code>
+ 雿踴艾U胯颯嫘怠潦畾菟扼具艾
+ <code class="directive"><a href="../mod/mod_authz_host.html#reject">Reject</a></code> 研胯
+ 皞艾具蝣箄艾整</p>
+
+
+
+ <h3><a name="filesystem" id="filesystem">U胯颯孵嗅鴃桀嫣</a></h3>
+ <p>隤閮潦准扎潦嫘格瑽隞亙雿輻具艾研胯
+ <code class="directive"><a href="../mod/mod_access_compat.html#order">Order</a></code>,
+ <code class="directive"><a href="../mod/mod_access_compat.html#allow">Allow</a></code>,
+ <code class="directive"><a href="../mod/mod_access_compat.html#deny">Deny</a></code>,
+ <code class="directive"><a href="../mod/mod_access_compat.html#satisfy">Satisfy</a></code>
+ 臬閬芥芥整
+ 具胯柴柴扎閮剖∼扎怒扼桀嫣扼靘
+ 柴研胯 <code class="module"><a href="../mod/mod_access_compat.html">mod_access_compat</a></code> U詻乓潦怒怎宏整</p>
+
+ <p>柴研胯格晞艾憿柴脯具扎怒輯株身摰銵具U胯颯孵嗅鴃株身摰銵
+ V具艾整具整
+ <code class="directive"><a href="../mod/mod_access_compat.html#satisfy">Satisfy</a></code> 研胯
+ 芥胯具嫘衣銝准扼芾澈潦喳箝具怒艾 2 扎桀衣畾菟蝯喋扎具整
+ 曉具胯柴研胯 <code class="module"><a href="../mod/mod_access_compat.html">mod_access_compat</a></code> 怎宏
+ 啜隤閮潦研胯典扎U胯颯孵嗅鴃研胯瘛瑯虫蝙具
+ 芥艾整桀憿柴<code class="module"><a href="../mod/mod_authz_default.html">mod_authz_default</a></code> U詻乓潦怒
+ 准潦具具艾閬扼敹怒芥艾整
+ <code class="module"><a href="../mod/mod_authz_default.html">mod_authz_default</a></code>U詻乓潦怒桐蜓芰桃胯押格輯准扎
+ 衣芥輯芥胯具嫘具怒整
+ 扎U胯颯孵嗅鴃研胯具游怒胯
+ U胯颯孵嗅鴃冽輯蝯喋扎艾嫘艾桀衣畾菟桀箏蝯閬艾U胯颯嫘怠潦瘙箝艾整
+ 扼扎研胯整雿芥游胯
+ <code class="module"><a href="../mod/mod_authz_default.html">mod_authz_default</a></code> 准潦艾芥芥
+ 函艾踴艾</p>
+
+
+
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="moreinformation" id="moreinformation">餈賢</a></h2>
+ <p>具艾押柴怠雿怒扎
+ 典格晞詻艾 <code class="module"><a href="../mod/mod_auth_basic.html">mod_auth_basic</a></code>
+ <code class="module"><a href="../mod/mod_authz_host.html">mod_authz_host</a></code>
+ 格詻隤准具扼
+ <code class="directive"><a href="../mod/mod_authn_core.html#&lt;authnprovideralias&gt;">&lt;AuthnProviderAlias&gt;</a></code>
+ 研胯雿踴具孵株閮潸身摰蝪∪急詻怒芥整</p>
+
+ <p><a href="access.html">U胯颯孵嗅鴃</a>格寞
+ a胯閮頛艾整柴扼閬扼</p>
+
+</div></div>
+<div class="bottomlang">
+<p><span>蝧餉迅皜輯隤: </span><a href="../en/howto/auth.html" hreflang="en" rel="alternate" title="English">&nbsp;en&nbsp;</a> |
+<a href="../es/howto/auth.html" hreflang="es" rel="alternate" title="Espa簽ol">&nbsp;es&nbsp;</a> |
+<a href="../fr/howto/auth.html" hreflang="fr" rel="alternate" title="Fran癟ais">&nbsp;fr&nbsp;</a> |
+<a href="../ja/howto/auth.html" title="Japanese">&nbsp;ja&nbsp;</a> |
+<a href="../ko/howto/auth.html" hreflang="ko" rel="alternate" title="Korean">&nbsp;ko&nbsp;</a> |
+<a href="../tr/howto/auth.html" hreflang="tr" rel="alternate" title="T羹rk癟e">&nbsp;tr&nbsp;</a></p>
+</div><div class="top"><a href="#page-header"><img src="../images/up.gif" alt="top" /></a></div><div class="section"><h2><a id="comments_section" name="comments_section">喋∼喋</a></h2><div class="warning"><strong>Notice:</strong><br />This is not a Q&amp;A section. Comments placed here should be pointed towards suggestions on improving the documentation or server, and may be removed by our moderators if they are either implemented or considered invalid/off-topic. Questions on how to manage the Apache HTTP Server should be directed at either our IRC channel, #httpd, on Libera.chat, or sent to our <a href="https://httpd.apache.org/lists.html">mailing lists</a>.</div>
+<script type="text/javascript"><!--//--><![CDATA[//><!--
+var comments_shortname = 'httpd';
+var comments_identifier = 'http://httpd.apache.org/docs/2.4/howto/auth.html';
+(function(w, d) {
+ if (w.location.hostname.toLowerCase() == "httpd.apache.org") {
+ d.write('<div id="comments_thread"><\/div>');
+ var s = d.createElement('script');
+ s.type = 'text/javascript';
+ s.async = true;
+ s.src = 'https://comments.apache.org/show_comments.lua?site=' + comments_shortname + '&page=' + comments_identifier;
+ (d.getElementsByTagName('head')[0] || d.getElementsByTagName('body')[0]).appendChild(s);
+ }
+ else {
+ d.write('<div id="comments_thread">Comments are disabled for this page at the moment.<\/div>');
+ }
+})(window, document);
+//--><!]]></script></div><div id="footer">
+<p class="apache">Copyright 2023 The Apache Software Foundation.<br />格詻 <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a> 柴押扎颯喋嫘扳靘艾整.</p>
+<p class="menu"><a href="../mod/">U詻乓潦</a> | <a href="../mod/directives.html">研胯</a> | <a href="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="../glossary.html">刻</a> | <a href="../sitemap.html">萸扎</a></p></div><script type="text/javascript"><!--//--><![CDATA[//><!--
+if (typeof(prettyPrint) !== 'undefined') {
+ prettyPrint();
+}
+//--><!]]></script>
+</body></html> \ No newline at end of file
diff --git a/docs/manual/howto/auth.html.ko.euc-kr b/docs/manual/howto/auth.html.ko.euc-kr
new file mode 100644
index 0000000..a6013b8
--- /dev/null
+++ b/docs/manual/howto/auth.html.ko.euc-kr
@@ -0,0 +1,355 @@
+<?xml version="1.0" encoding="EUC-KR"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="ko" xml:lang="ko"><head>
+<meta content="text/html; charset=EUC-KR" http-equiv="Content-Type" />
+<!--
+ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+ This file is generated from xml source: DO NOT EDIT
+ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+ -->
+<title>檣隸(Authentication), 掏и睡罹(Authorization),
+蕾斬薯橫(Access Control) - Apache HTTP Server Version 2.4</title>
+<link href="../style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" />
+<link href="../style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" />
+<link href="../style/css/manual-print.css" rel="stylesheet" media="print" type="text/css" /><link rel="stylesheet" type="text/css" href="../style/css/prettify.css" />
+<script src="../style/scripts/prettify.min.js" type="text/javascript">
+</script>
+
+<link href="../images/favicon.ico" rel="shortcut icon" /></head>
+<body id="manual-page"><div id="page-header">
+<p class="menu"><a href="../mod/">賅菊</a> | <a href="../mod/directives.html">雖衛橫菟</a> | <a href="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="../glossary.html">辨橫</a> | <a href="../sitemap.html">餌檜お裘</a></p>
+<p class="apache">Apache HTTP Server Version 2.4</p>
+<img alt="" src="../images/feather.png" /></div>
+<div class="up"><a href="./"><img title="&lt;-" alt="&lt;-" src="../images/left.gif" /></a></div>
+<div id="path">
+<a href="http://www.apache.org/">Apache</a> &gt; <a href="http://httpd.apache.org/">HTTP Server</a> &gt; <a href="http://httpd.apache.org/docs/">Documentation</a> &gt; <a href="../">Version 2.4</a> &gt; <a href="./">How-To / Tutorials</a></div><div id="page-content"><div id="preamble"><h1>檣隸(Authentication), 掏и睡罹(Authorization),
+蕾斬薯橫(Access Control)</h1>
+<div class="toplang">
+<p><span>陛棟и 樹橫: </span><a href="../en/howto/auth.html" hreflang="en" rel="alternate" title="English">&nbsp;en&nbsp;</a> |
+<a href="../es/howto/auth.html" hreflang="es" rel="alternate" title="Espa&#241;ol">&nbsp;es&nbsp;</a> |
+<a href="../fr/howto/auth.html" hreflang="fr" rel="alternate" title="Fran&#231;ais">&nbsp;fr&nbsp;</a> |
+<a href="../ja/howto/auth.html" hreflang="ja" rel="alternate" title="Japanese">&nbsp;ja&nbsp;</a> |
+<a href="../ko/howto/auth.html" title="Korean">&nbsp;ko&nbsp;</a> |
+<a href="../tr/howto/auth.html" hreflang="tr" rel="alternate" title="T&#252;rk&#231;e">&nbsp;tr&nbsp;</a></p>
+</div>
+<div class="outofdate">檜 僥憮朝 譆褐っ 廓羲檜 嬴椎棲棻.
+ 譆斬縑 滲唳脹 頂辨擎 艙橫 僥憮蒂 霤堅ж撮蹂.</div>
+
+ <p>檣隸(authentication)擎 濠褐檜 援掘塭堅 輿濰ж朝 餌塋擊
+ 挫恉炴 瞰離檜棻. 掏и睡罹(authorization)朝 陛堅 談擎 夠戲煎
+ 陛紫煙 分 錳ж朝 薑爾蒂 橢紫煙 ъ辨ж朝 婁薑檜棻.</p>
+</div>
+<div id="quickview"><a href="https://www.apache.org/foundation/contributing.html" class="badge"><img src="https://www.apache.org/images/SupportApache-small.png" alt="Support Apache!" /></a><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#related">婦溼 賅菊婁 雖衛橫</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#introduction">模偃</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#theprerequisites">晦獄 雖衝</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#gettingitworking">晦獄瞳檣 撲薑ж晦</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#lettingmorethanonepersonin">罹楝貲擊 菟罹爾頂晦</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#possibleproblems">嫦儅й 熱 氈朝 僥薯薄</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#whatotherneatstuffcanido">棻艇 寞徹紫 陛棟и陛?</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#moreinformation">渦 號擎 薑爾</a></li>
+</ul><h3>霤堅</h3><ul class="seealso"><li><a href="#comments_section">Comments</a></li></ul></div>
+<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="related" id="related">婦溼 賅菊婁 雖衛橫</a></h2>
+ <table class="related"><tr><th>婦溼脹 賅菊</th><th>婦溼脹 雖衛橫</th></tr><tr><td><ul><li><code class="module"><a href="../mod/mod_auth_basic.html">mod_auth_basic</a></code></li><li><code class="module"><a href="../mod/mod_authn_file.html">mod_authn_file</a></code></li><li><code class="module"><a href="../mod/mod_authz_groupfile.html">mod_authz_groupfile</a></code></li><li><code class="module"><a href="../mod/mod_authz_host.html">mod_authz_host</a></code></li></ul></td><td><ul><li><code class="directive"><a href="../mod/mod_authz_host.html#allow">Allow</a></code></li><li><code class="directive"><a href="../mod/mod_authz_groupfile.html#authgroupfile">AuthGroupFile</a></code></li><li><code class="directive"><a href="../mod/core.html#authname">AuthName</a></code></li><li><code class="directive"><a href="../mod/core.html#authtype">AuthType</a></code></li><li><code class="directive"><a href="../mod/mod_authn_file.html#authuserfile">AuthUserFile</a></code></li><li><code class="directive"><a href="../mod/mod_authz_host.html#deny">Deny</a></code></li><li><code class="directive"><a href="../mod/core.html#options">Options</a></code></li><li><code class="directive"><a href="../mod/core.html#require">Require</a></code></li></ul></td></tr></table>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="introduction" id="introduction">模偃</a></h2>
+ <p>渡褐曖 壎餌檜お縑 氈朝 薑爾陛 模熱曖 餌塋菟虜曖 綠塵檜剪釭
+ 檜菟虜擊 嬪и 薑爾塭賊, 檜 旋縑憮 撲貲ж朝 晦徹擊 餌辨ж罹
+ 渡褐檜 爾望 錳ж朝 餌塋虜 む檜雖蒂 爾紫煙 й 熱 氈棻.</p>
+
+ <p>檜 旋擎 壎餌檜お曖 橾睡蒂 爾ж晦嬪п 號擎 餌塋菟檜
+ 餌辨ж朝 "ル遽瞳檣" 寞徹擊 棻琿棻.</p>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="theprerequisites" id="theprerequisites">晦獄 雖衝</a></h2>
+ <p>檜 旋縑憮 棻瑞朝 雖衛橫朝 憮幗曖 輿撲薑だ橾(橾奩瞳戲煎
+ <code class="directive"><a href="../mod/core.html#directory">&lt;Directory&gt;</a></code>
+ 播暮)檜釭 蛤滓饜葬滌 撲薑だ橾(<code>.htaccess</code> だ橾)縑憮
+ 餌辨и棻.</p>
+
+ <p><code>.htaccess</code> だ橾擊 餌辨ж溥賊 檜 だ橾縑 氈朝
+ 檣隸 雖衛橫蒂 ъ辨ж紫煙 憮幗蒂 撲薑п撿 и棻. 檜蒂 嬪п
+ 蛤滓饜葬滌 撲薑だ橾縑 橫雯 雖衛橫蒂 餌辨й 熱 氈朝雖蒂 唸薑ж朝
+ <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code> 雖衛橫蒂
+ 餌辨и棻.</p>
+
+ <p>罹晦憮朝 檣隸擊 棻瑞晦 陽僥縑, 棻擠婁 偽擎
+ <code>AllowOverride</code> 雖衛橫陛 в蹂ж棻.</p>
+
+ <div class="example"><p><code>
+ AllowOverride AuthConfig
+ </code></p></div>
+
+ <p>分 雖衛橫蒂 霜蕾 憮幗 輿撲薑だ橾縑 瞳朝棻賊, 斜 だ橾縑
+ 噙晦 掏и檜 僭煩 氈橫撿 и棻.</p>
+
+ <p>斜葬堅 爾й だ橾檜 橫蛤氈朝雖 憲晦嬪п 憮幗曖 蛤滓饜葬
+ 掘褻縑 渠п 褻旎 憲嬴撿и棻. 檜 橾擎 橫滑雖彊堅, 瞳渡и
+ 陽縑 濠撮 撲貲й 匙檜棻.</p>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="gettingitworking" id="gettingitworking">晦獄瞳檣 撲薑ж晦</a></h2>
+ <p>檜薯 憮幗曖 蛤滓饜葬蒂 懍ㄦ 爾ж朝 晦獄瞳檣 寞徹擊
+ 撲貲и棻.</p>
+
+ <p>試盪 懍だ橾擊 虜菟橫撿 и棻. 檜 だ橾擎 壎縑憮 蕾斬й
+ 熱 橈朝 夠縑 氈橫撿 и棻. 棻艇餌塋檜 懍だ橾擊 棻遴煎萄ж雖
+ 跤ж啪ж晦 嬪п憮棻. 蕨蒂 菟橫, 僥憮菟檜
+ <code>/usr/local/apache/htdocs</code>縑 氈棻賊 懍だ橾(菟)擎
+ <code>/usr/local/apache/passwd</code>縑 菩棻.</p>
+
+ <p>嬴だ纂縑 んл脹 <a href="../programs/htpasswd.html">htpasswd</a> 紫掘蒂 餌辨ж罹
+ 懍だ橾擊 虜萇棻. 檜 Щ煎斜極擎 嬴だ纂蒂 撲纂и 夠曖
+ <code>bin</code> 蛤滓饜葬縑 氈棻. だ橾擊 虜菟溥賊 棻擠婁
+ 偽檜 殮溘и棻.</p>
+
+ <div class="example"><p><code>
+ htpasswd -c /usr/local/apache/passwd/passwords rbowen
+ </code></p></div>
+
+ <p><code>htpasswd</code>朝 懍ㄧ 僭橫爾堅, 挫怹 嬪п
+ 懍ㄧ 棻衛 殮溘ж塭堅 蹂羶и棻.</p>
+
+ <div class="example"><p><code>
+ # htpasswd -c /usr/local/apache/passwd/passwords rbowen<br />
+ New password: mypassword<br />
+ Re-type new password: mypassword<br />
+ Adding password for user rbowen
+ </code></p></div>
+
+ <p>僭煩 <code>htpasswd</code>檜 褒чだ橾 唳煎縑 橈棻賊
+ 褒чだ橾曖 瞪羹 唳煎蒂 殮溘п撿 и棻. 頂陛 餌辨ж朝 憮幗縑憮朝
+ <code>/usr/local/apache/bin/htpasswd</code>縑 褒чだ橾檜
+ 氈棻.</p>
+
+ <p>棻擠戲煎 憮幗陛 懍ㄧ 蹂羶ж紫煙 撲薑ж堅, 憮幗縑啪
+ 橫雯 餌辨濠曖 蕾斬擊 ъ辨й雖 憲溥醜撿 и棻.
+ <code>httpd.conf</code>蒂 ら餵ж剪釭 <code>.htaccess</code>
+ だ橾擊 餌辨ж罹 撲薑и棻. 蕨蒂 菟橫,
+ <code>/usr/local/apache/htdocs/secret</code> 蛤滓饜葬蒂
+ 爾ж溥賊, 嬴楚 雖衛橫蒂
+ <code>/usr/local/apache/htdocs/secret/.htaccess</code> だ橾檜釭
+ <code>httpd.conf</code>曖 &lt;Directory
+ /usr/local/apache/apache/htdocs/secret&gt; 播暮縑 瞳橫撿
+ и棻.</p>
+
+ <div class="example"><p><code>
+ AuthType Basic<br />
+ AuthName "Restricted Files"<br />
+ AuthUserFile /usr/local/apache/passwd/passwords<br />
+ Require user rbowen
+ </code></p></div>
+
+ <p>雖衛橫蒂 ж釭噶 髦よ爾濠. <code class="directive"><a href="../mod/core.html#authtype">AuthType</a></code> 雖衛橫朝 餌辨濠蒂 檣隸й
+ 寞徹擊 摹鷗и棻. 陛濰 橾奩瞳檣 寞徹擎 <code>Basic</code>戲煎,
+ <code class="module"><a href="../mod/mod_auth_basic.html">mod_auth_basic</a></code>檜 掘⑷и棻. 斜楝釭 Basic
+ 檣隸擎 粽塭辦盪陛 憮幗煎 懍ㄧ 懍倆狫 彊堅 爾魚棻.
+ 斜楝嘎煎 晦塵 濠猿蒂 爾ж晦嬪п 檜 寞徹擊 餌辨ж賊 寰脹棻.
+ 嬴だ纂朝 <code>AuthType Digest</code>塭朝 檣隸 寞徹紫 雖錳и棻.
+ 檜 寞徹擎 <code class="module"><a href="../mod/mod_auth_digest.html">mod_auth_digest</a></code>陛 掘⑷ж貊, 衙辦
+ 寰瞪ж棻. 陛濰 譆斬 贗塭檜樹お菟虜檜 Digest 檣隸擊 雖錳и棻堅
+ и棻.</p>
+
+ <p><code class="directive"><a href="../mod/core.html#authname">AuthName</a></code> 雖衛橫朝
+ 檣隸縑 餌辨й <dfn>艙羲(realm)</dfn>擊 雖薑и棻. 艙羲擎
+ 舒陛雖 羲й擊 и棻. 羅廓簞朝 贗塭檜樹お陛 爾鱔 檜 薑爾蒂
+ 懍 渠倥Ⅶ 爾罹遽棻. 舒廓簞朝 艙羲 薑爾蒂 餌辨ж罹
+ 贗塭檜樹お陛 か薑 檣隸掘羲縑 橫雯 懍ㄧ 爾鳥雖 唸薑и棻.</p>
+
+ <p>蕨蒂 菟橫, 橾欽 贗塭檜樹お陛 <code>"Restricted Files"</code>
+ 艙羲縑 檣隸檜 撩奢ж艘棻賊, 贗塭檜樹お朝 濠翕戲煎 偽擎 憮幗縑憮
+ <code>"Restricted Files"</code> 艙羲戲煎 ル衛脹 掘羲縑 渠п
+ 翕橾и 懍ㄧ 衛紫и棻. 斜楚憮 罹楝 薯и 掘羲檜 偽擎 艙羲擊
+ 奢嶸ж賊 餌辨濠陛 罹楝廓 懍ㄧ 殮溘ж雖 彊嬴紫 脹棻. 僭煩
+ 爾寰鼻 檜嶸煎 贗塭檜樹お朝 憮幗曖 ˊ瘋捂簎 棻腦賊 о鼻
+ 億煎 懍ㄧ 僭橫獄棻.</p>
+
+ <p><code class="directive"><a href="../mod/mod_authn_file.html#authuserfile">AuthUserFile</a></code>
+ 雖衛橫朝 辦葬陛 寞旎 <code>htpasswd</code>煎 虜萇 懍だ橾曖
+ 唳煎蒂 撲薑и棻. 餌辨濠陛 號棻賊 蹂羶葆棻 衙廓 餌辨濠蒂
+ 檣隸ж晦嬪п 橾奩 僥憮だ橾擊 匐儀ж朝等 衛除檜 鼻渡 號檜
+ 勘萵 熱 氈棻. 嬴だ纂朝 緒艇 等檜顫漆檜蝶 だ橾縑 餌辨濠 薑爾蒂
+ 盪濰й 熱 氈棻. <code class="module"><a href="../mod/mod_authn_dbm.html">mod_authn_dbm</a></code> 賅菊擎 <code class="directive"><a href="../mod/mod_authn_dbm.html#authdbmuserfile">AuthDBMUserFile</a></code> 雖衛橫蒂
+ 薯奢и棻. <a href="../programs/dbmmanage.html">dbmmanage</a>
+ Щ煎斜極擊 餌辨ж罹 懍だ橾擊 虜菟堅 棻琿棻. <a href="http://modules.apache.org/">嬴だ纂 賅菊
+ 等檜顫漆檜蝶</a>縑朝 罹楝 棻艇 檣隸 寞衝擊 薯奢ж朝 薯鳴濠陛
+ 虜萇 賅菊菟檜 氈棻.</p>
+
+ <p>葆雖虞戲煎 <code class="directive"><a href="../mod/core.html#require">Require</a></code>
+ 雖衛橫朝 憮幗曖 か薑 艙羲縑 蕾斬й 熱 氈朝 餌辨濠蒂 雖薑ж罹
+ 掏и睡罹蒂 и棻. 棻擠 瞰擎 <code>require</code> 雖衛橫蒂
+ 餌辨ж朝 棻曄и 寞徹擊 撲貲и棻.</p>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="lettingmorethanonepersonin" id="lettingmorethanonepersonin">罹楝貲擊 菟罹爾頂晦</a></h2>
+ <p>嬪曖 雖衛橫朝 蛤滓饜葬煎 (餌辨濠貲檜 <code>rbowen</code>檣)
+ и 餌塋虜擊 菟罹爾魚棻. 渠睡碟曖 唳辦 罹楝 餌塋擊 菟罹爾頂堅
+ 談擊 匙檜棻. 檜薯 <code class="directive"><a href="../mod/mod_authz_groupfile.html#authgroupfile">AuthGroupFile</a></code>擊
+ 餌辨й 陽棻.</p>
+
+ <p>罹楝 餌塋擊 菟罹爾頂堅 談棻賊 斜瑜貲婁 斜 斜瑜縑 橫雯
+ 餌辨濠菟檜 氈朝雖 憲溥輿朝 斜瑜だ橾檜 в蹂ж棻. 檜 だ橾曖
+ ⑽衝擎 衙辦 除欽ж罹, 嬴鼠 ら餵晦煎釭 虜菟 熱 氈棻. だ橾頂辨擎
+ 棻擠婁 偽棻.</p>
+
+ <div class="example"><p><code>
+ GroupName: rbowen dpitts sungo rshersey
+ </code></p></div>
+
+ <p>斜傖 奢寥戲煎 掘碟и 曹 斜瑜 掘撩錳 跡煙橾 閨檜棻.</p>
+
+ <p>晦襄曖 懍だ橾縑 餌辨濠蒂 蹺陛ж溥賊 棻擠婁 偽檜 殮溘и棻</p>
+
+ <div class="example"><p><code>
+ htpasswd /usr/local/apache/passwd/passwords dpitts
+ </code></p></div>
+
+ <p>瞪婁 偽雖虜, 億煎 だ橾擊 虜菟雖 彊堅 晦襄 だ橾縑 餌辨濠蒂
+ 蹺陛и棻. (<code>-c</code> 褫暮擎 億煎 懍だ橾擊 虜萇棻).</p>
+
+ <p>檜薯 <code>.htaccess</code> だ橾擊 棻擠婁 偽檜 熱薑и棻.</p>
+
+ <div class="example"><p><code>
+ AuthType Basic<br />
+ AuthName "By Invitation Only"<br />
+ AuthUserFile /usr/local/apache/passwd/passwords<br />
+ AuthGroupFile /usr/local/apache/passwd/groups<br />
+ Require group GroupName
+ </code></p></div>
+
+ <p>斜楝賊 <code>GroupName</code> 斜瑜縑 樓ж貊
+ <code>password</code> だ橾縑 о跡檜 氈朝 餌辨濠陛 螢夥艇
+ 懍ㄧ 殮溘ж賊 蕾斬擊 ъ辨и棻.</p>
+
+ <p>罹楝 橾奩 餌辨濠蒂 菟罹爾頂朝 棻艇 寞徹檜 氈棻. 斜瑜だ橾擊
+ 虜菟 в蹂橈檜 棻擠 雖衛橫蒂 餌辨ж晦虜 ж賊 脹棻.</p>
+
+ <div class="example"><p><code>
+ Require valid-user
+ </code></p></div>
+
+ <p><code>Require user rbowen</code> 渠褐 檜 雖衛橫蒂 餌辨ж賊
+ 懍だ橾縑 氈朝 援掘塭紫 螢夥艇 懍ㄧ 殮溘ж晦虜 ж賊 蕾斬擊
+ ъ辨и棻. 斜瑜滌煎 棻艇 懍だ橾擊 餌辨ж罹 斜瑜婁 綠蝌и
+ 膩蒂 橢擊 熱紫 氈棻. 檜 唳辦 嬴だ纂陛 だ橾 舒偃(懍だ橾婁
+ 斜瑜だ橾)陛 嬴棋 だ橾 и偃(懍だ橾)虜 匐餌ж賊 脹棻朝 匙檜
+ 濰薄檜棻. 斜楝釭 罹楝 懍だ橾擊 婦葬п撿 ж堅, <code class="directive"><a href="../mod/mod_authn_file.html#authuserfile">AuthUserFile</a></code> 雖衛橫縑
+ 薑旁 懍だ橾擊 雖薑п撿 ж朝 匙擎 欽薄檜棻.</p>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="possibleproblems" id="possibleproblems">嫦儅й 熱 氈朝 僥薯薄</a></h2>
+ <p>Basic 檣隸 寞衝擎 憮幗縑憮 僥憮蒂 蹂羶й 陽葆棻 餌辨濠貲婁
+ 懍ㄧ 挫恉挬. 褕雖橫 偽擎 む檜雖蒂 億煎 堅藹й 陽紫 む檜雖諦
+ (斜葡檜 懍ㄦ 爾ж朝 蛤滓饜葬縑 氈朝 唳辦) む檜雖縑 氈朝
+ 賅萇 斜葡縑 渠п 棻衛 挫恉挬. 颶濛ж蛭檜 樓紫陛 褻旎 替溥霞棻.
+ 懍だ橾擊 翮橫憮 餌辨濠貲擊 瓊擊 陽梱雖 餌辨濠 跡煙擊 髦よ瑭撿
+ ж晦陽僥縑 懍だ橾 觼晦陛 醴韓 熱煙 渦 替溥霞棻. 斜葬堅
+ 檜 濛機擊 む檜雖蒂 蹂羶й 陽葆棻 霞чи棻.</p>
+
+ <p>斜楚憮 ⑷褒瞳戲煎 и 懍だ橾縑 盪濰й 熱 氈朝 餌辨濠熱縑朝
+ и啗陛 氈棻. 檜 и啗朝 餌辨ж朝 憮幗曖 撩棟縑 評塭 棻腦雖虜,
+ о跡檜 熱寥偃陛 剩朝棻賊 替溥霞棻堅 儅陝ж堅 棻艇 檣隸 寞徹擊
+ 堅溥п撿 и棻.</p>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="whatotherneatstuffcanido" id="whatotherneatstuffcanido">棻艇 寞徹紫 陛棟и陛?</a></h2>
+ <p>餌辨濠貲婁 懍ㄧ 餌辨и 檣隸檜 棻陛 嬴棲棻. 謙謙 蕾樓и
+ 濰模諦 偽擎 棻艇 薑爾蒂 陛雖堅 餌辨濠蒂 菟罹爾頂堅 談擊
+ 陽陛 氈棻.</p>
+
+ <p><code class="directive"><a href="../mod/mod_authz_host.html#allow">Allow</a></code>諦
+ <code class="directive"><a href="../mod/mod_authz_host.html#deny">Deny</a></code> 雖衛橫朝
+ 僥憮蒂 蹂羶и 闡У攪曖 ˊ瘋捂 分 ˊ瘋 輿模蒂 陛雖堅
+ 蕾斬擊 ъ辨ж剪釭 剪睡и棻. <code class="directive"><a href="../mod/mod_authz_host.html#order">Order</a></code> 雖衛橫朝 檜 舒
+ 雖衛橫諦 偽檜 餌辨ж罹, 嬴だ纂縑啪 橫雯 牖憮煎 敘罌擊 瞳辨й雖
+ 憲萼棻.</p>
+
+ <p>檜菟 雖衛橫 餌辨徹擎 棻擠婁 偽棻.</p>
+
+ <div class="example"><p><code>
+ Allow from <var>address</var>
+ </code></p></div>
+
+ <p>罹晦憮 <var>address</var>朝 IP 輿模(分 IP 輿模 橾睡)釭
+ 諫瞪и 紫詭檣貲(分 紫詭檣貲 橾睡)檜棻. 錳и棻賊 罹楝 輿模釭
+ 紫詭檣貲擊 餌辨й 熱 氈棻.</p>
+
+ <p>蕨蒂 菟橫, 援捱陛陛 啪衛っ縑 惜堅蒂 螢葬堅 氈棻賊 棻擠婁
+ 偽檜 蕾斬擊 虞擊 熱 氈棻.</p>
+
+ <div class="example"><p><code>
+ Deny from 205.252.46.165
+ </code></p></div>
+
+ <p>斜 輿模縑憮 菟橫螃朝 寞僥濠朝 檜 雖衛橫陛 爾ж朝 む檜雖蒂
+ 獐 熱 橈棻. IP 輿模 渠褐 棻擠婁 偽檜 闡У攪貲擊 餌辨й 熱紫
+ 氈棻.</p>
+
+ <div class="example"><p><code>
+ Deny from <var>host.example.com</var>
+ </code></p></div>
+
+ <p>傳, 瞪羹 紫詭檣曖 蕾斬擊 虞戲溥賊 輿模釭 紫詭檣貲曖 橾睡蒂
+ 餌辨и棻.</p>
+
+ <div class="example"><p><code>
+ Deny from <var>192.101.205</var><br />
+ Deny from <var>cyberthugs.com</var> <var>moreidiots.com</var><br />
+ Deny from ke
+ </code></p></div>
+
+ <p><code class="directive"><a href="../mod/mod_authz_host.html#order">Order</a></code>蒂
+ <code class="directive"><a href="../mod/mod_authz_host.html#deny">Deny</a></code>諦 <code class="directive"><a href="../mod/mod_authz_host.html#allow">Allow</a></code> 雖衛橫諦 偽檜
+ 餌辨ж罹 褒薯煎 錳ж朝 渠鼻擊 虞擊 熱 氈棻.</p>
+
+ <div class="example"><p><code>
+ Order deny,allow<br />
+ Deny from all<br />
+ Allow from <var>dev.example.com</var>
+ </code></p></div>
+
+ <p><code class="directive"><a href="../mod/mod_authz_host.html#allow">Allow</a></code>
+ 雖衛橫虜 餌辨ж賊, п渡 ˊ瘋挫 餌辨濠蒂 ъ辨ж堅 剪晦縑
+ 蹺陛煎 賅萇 餌塋擊 ъ辨ж嘎煎 錳ж朝 唸婁蒂 橢雖 跤и棻.
+ 渡褐擎 か薑 餌塋<em>虜</em> ъ辨ж望 錳и棻.</p>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="moreinformation" id="moreinformation">渦 號擎 薑爾</a></h2>
+ <p><code class="module"><a href="../mod/mod_auth_basic.html">mod_auth_basic</a></code>婁
+ <code class="module"><a href="../mod/mod_authz_host.html">mod_authz_host</a></code> 僥憮縑 蕾斬薯橫陛 翕濛ж朝
+ 寞徹縑 渠и 渦 號擎 薑爾陛 氈棻.</p>
+</div></div>
+<div class="bottomlang">
+<p><span>陛棟и 樹橫: </span><a href="../en/howto/auth.html" hreflang="en" rel="alternate" title="English">&nbsp;en&nbsp;</a> |
+<a href="../es/howto/auth.html" hreflang="es" rel="alternate" title="Espa&#241;ol">&nbsp;es&nbsp;</a> |
+<a href="../fr/howto/auth.html" hreflang="fr" rel="alternate" title="Fran&#231;ais">&nbsp;fr&nbsp;</a> |
+<a href="../ja/howto/auth.html" hreflang="ja" rel="alternate" title="Japanese">&nbsp;ja&nbsp;</a> |
+<a href="../ko/howto/auth.html" title="Korean">&nbsp;ko&nbsp;</a> |
+<a href="../tr/howto/auth.html" hreflang="tr" rel="alternate" title="T&#252;rk&#231;e">&nbsp;tr&nbsp;</a></p>
+</div><div class="top"><a href="#page-header"><img src="../images/up.gif" alt="top" /></a></div><div class="section"><h2><a id="comments_section" name="comments_section">Comments</a></h2><div class="warning"><strong>Notice:</strong><br />This is not a Q&amp;A section. Comments placed here should be pointed towards suggestions on improving the documentation or server, and may be removed by our moderators if they are either implemented or considered invalid/off-topic. Questions on how to manage the Apache HTTP Server should be directed at either our IRC channel, #httpd, on Libera.chat, or sent to our <a href="https://httpd.apache.org/lists.html">mailing lists</a>.</div>
+<script type="text/javascript"><!--//--><![CDATA[//><!--
+var comments_shortname = 'httpd';
+var comments_identifier = 'http://httpd.apache.org/docs/2.4/howto/auth.html';
+(function(w, d) {
+ if (w.location.hostname.toLowerCase() == "httpd.apache.org") {
+ d.write('<div id="comments_thread"><\/div>');
+ var s = d.createElement('script');
+ s.type = 'text/javascript';
+ s.async = true;
+ s.src = 'https://comments.apache.org/show_comments.lua?site=' + comments_shortname + '&page=' + comments_identifier;
+ (d.getElementsByTagName('head')[0] || d.getElementsByTagName('body')[0]).appendChild(s);
+ }
+ else {
+ d.write('<div id="comments_thread">Comments are disabled for this page at the moment.<\/div>');
+ }
+})(window, document);
+//--><!]]></script></div><div id="footer">
+<p class="apache">Copyright 2023 The Apache Software Foundation.<br />Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p>
+<p class="menu"><a href="../mod/">賅菊</a> | <a href="../mod/directives.html">雖衛橫菟</a> | <a href="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="../glossary.html">辨橫</a> | <a href="../sitemap.html">餌檜お裘</a></p></div><script type="text/javascript"><!--//--><![CDATA[//><!--
+if (typeof(prettyPrint) !== 'undefined') {
+ prettyPrint();
+}
+//--><!]]></script>
+</body></html> \ No newline at end of file
diff --git a/docs/manual/howto/auth.html.tr.utf8 b/docs/manual/howto/auth.html.tr.utf8
new file mode 100644
index 0000000..fda3281
--- /dev/null
+++ b/docs/manual/howto/auth.html.tr.utf8
@@ -0,0 +1,639 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="tr" xml:lang="tr"><head>
+<meta content="text/html; charset=UTF-8" http-equiv="Content-Type" />
+<!--
+ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+ This file is generated from xml source: DO NOT EDIT
+ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+ -->
+<title>Kimlik Dorulama ve Yetkilendirme - Apache HTTP Sunucusu S羹r羹m 2.4</title>
+<link href="../style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" />
+<link href="../style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" />
+<link href="../style/css/manual-print.css" rel="stylesheet" media="print" type="text/css" /><link rel="stylesheet" type="text/css" href="../style/css/prettify.css" />
+<script src="../style/scripts/prettify.min.js" type="text/javascript">
+</script>
+
+<link href="../images/favicon.ico" rel="shortcut icon" /></head>
+<body id="manual-page"><div id="page-header">
+<p class="menu"><a href="../mod/">Mod羹ller</a> | <a href="../mod/directives.html">Y繹nergeler</a> | <a href="http://wiki.apache.org/httpd/FAQ">SSS</a> | <a href="../glossary.html">Terimler</a> | <a href="../sitemap.html">Site Haritas覺</a></p>
+<p class="apache">Apache HTTP Sunucusu S羹r羹m 2.4</p>
+<img alt="" src="../images/feather.png" /></div>
+<div class="up"><a href="./"><img title="&lt;-" alt="&lt;-" src="../images/left.gif" /></a></div>
+<div id="path">
+<a href="http://www.apache.org/">Apache</a> &gt; <a href="http://httpd.apache.org/">HTTP Sunucusu</a> &gt; <a href="http://httpd.apache.org/docs/">Belgeleme</a> &gt; <a href="../">S羹r羹m 2.4</a> &gt; <a href="./">Nas覺llar ve reticiler</a></div><div id="page-content"><div id="preamble"><h1>Kimlik Dorulama ve Yetkilendirme</h1>
+<div class="toplang">
+<p><span>Mevcut Diller: </span><a href="../en/howto/auth.html" hreflang="en" rel="alternate" title="English">&nbsp;en&nbsp;</a> |
+<a href="../es/howto/auth.html" hreflang="es" rel="alternate" title="Espa簽ol">&nbsp;es&nbsp;</a> |
+<a href="../fr/howto/auth.html" hreflang="fr" rel="alternate" title="Fran癟ais">&nbsp;fr&nbsp;</a> |
+<a href="../ja/howto/auth.html" hreflang="ja" rel="alternate" title="Japanese">&nbsp;ja&nbsp;</a> |
+<a href="../ko/howto/auth.html" hreflang="ko" rel="alternate" title="Korean">&nbsp;ko&nbsp;</a> |
+<a href="../tr/howto/auth.html" title="T羹rk癟e">&nbsp;tr&nbsp;</a></p>
+</div>
+
+ <p>Kimlik Dorulama istediiniz kiileri teyid etme ilemidir.
+ Yetkilendirme ise kiilerin nereye gireceklerine ve hangi bilgiye
+ ulaacaklar覺na m羹saade edilmesi ilemidir.</p>
+
+ <p>Genel eriim denetimi i癟in <a href="access.html">Eriim Denetimi
+ Nas覺l</a> belgesine bak覺n覺z.</p>
+</div>
+<div id="quickview"><a href="https://www.apache.org/foundation/contributing.html" class="badge"><img src="https://www.apache.org/images/SupportApache-small.png" alt="Support Apache!" /></a><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#related">襤lgili mod羹ller ve Y繹nergeler</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#introduction">Giri</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#theprerequisites">n gereksinimler</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#gettingitworking">al覺maya Balama</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#lettingmorethanonepersonin">Birden 癟ok kiiye izin vermek</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#possibleproblems">Olas覺 Sorunlar</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#dbmdbd">Dier parola depolama y繹ntemleri</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#multprovider">Birden 癟ok tedarik癟i kullanmak</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#beyond">Yetkilendirmenin biraz 繹tesi</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#socache">Kimlik Dorulama Arabellei</a></li>
+<li><img alt="" src="../images/down.gif" /> <a href="#moreinformation">Daha fazla bilgi</a></li>
+</ul><h3>Ayr覺ca bak覺n覺z:</h3><ul class="seealso"><li><a href="#comments_section">Yorumlar</a></li></ul></div>
+<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="related" id="related">襤lgili mod羹ller ve Y繹nergeler</a></h2>
+
+ <p>Kimlik Dorulama ve yetkilendirme ilemi ile ilgili 羹癟 t羹r mod羹l
+ vard覺r. Genellikle her bir gruptan en az bir mod羹l se癟eceksiniz.</p>
+
+ <ul>
+ <li>Kimlik Dorulama t羹r羹 (bkz. <code class="directive"><a href="../mod/mod_authn_core.html#authtype">AuthType</a></code> y繹nergesi)
+ <ul>
+ <li><code class="module"><a href="../mod/mod_auth_basic.html">mod_auth_basic</a></code></li>
+ <li><code class="module"><a href="../mod/mod_auth_digest.html">mod_auth_digest</a></code></li>
+ </ul>
+ </li>
+
+ <li>Kimlik Dorulay覺c覺 (bkz.
+ <code class="directive"><a href="../mod/mod_auth_basic.html#authbasicprovider">AuthBasicProvider</a></code>
+ ve <code class="directive"><a href="../mod/mod_auth_digest.html#authdigestprovider">AuthDigestProvider</a></code> y繹nergeleri)
+ <ul>
+ <li><code class="module"><a href="../mod/mod_authn_anon.html">mod_authn_anon</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authn_dbd.html">mod_authn_dbd</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authn_dbm.html">mod_authn_dbm</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authn_file.html">mod_authn_file</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authnz_ldap.html">mod_authnz_ldap</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authn_socache.html">mod_authn_socache</a></code></li>
+ </ul>
+ </li>
+ <li>Yetkilendirme (bkz.
+ <code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code> y繹nergesi)
+ <ul>
+ <li><code class="module"><a href="../mod/mod_authnz_ldap.html">mod_authnz_ldap</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authz_dbd.html">mod_authz_dbd</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authz_dbm.html">mod_authz_dbm</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authz_groupfile.html">mod_authz_groupfile</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authz_host.html">mod_authz_host</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authz_owner.html">mod_authz_owner</a></code></li>
+ <li><code class="module"><a href="../mod/mod_authz_user.html">mod_authz_user</a></code></li>
+ </ul>
+ </li>
+ </ul>
+
+ <p>Bu mod羹llere ek olarak, <code class="module"><a href="../mod/mod_authn_core.html">mod_authn_core</a></code> ve
+ <code class="module"><a href="../mod/mod_authz_core.html">mod_authz_core</a></code> mod羹lleri bulunur. Bu mod羹ller
+ yetkilendirme mod羹llerinin 癟ekirdeini oluturan temel y繹nergeleri
+ ger癟ekler.</p>
+
+ <p><code class="module"><a href="../mod/mod_authnz_ldap.html">mod_authnz_ldap</a></code> mod羹l羹 kimlik dorulama ve
+ yetkilendirme ilemlerinin ikisini birden ger癟ekletirir.
+ <code class="module"><a href="../mod/mod_authz_host.html">mod_authz_host</a></code> mod羹l羹 bu ilemleri sunucu ad覺na, IP
+ adresine ve istein karekteristiine bal覺 olarak ger癟ekletirir.
+ Ancak kimlik dorulama sisteminin bir par癟as覺 deildir.
+ <code>mod_access</code> ile geriye uyumluluk i癟in
+ <code class="module"><a href="../mod/mod_access_compat.html">mod_access_compat</a></code> diye bir mod羹l daha vard覺r.</p>
+
+ <p>Muhtemelen g繹z atmak isteyeceiniz <a href="access.html">Eriim
+ Denetimi</a> nas覺l belgesi, sunucuya eriimlerin 癟eitli yollar覺ndan
+ bahsetmektedir.</p>
+ </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="introduction" id="introduction">Giri</a></h2>
+ <p>Sitenizde sadece k羹癟羹k bir grup insana hitap eden ya da hassas
+ bilgileriniz varsa, bu makaledeki teknikleri kullanarak dilediiniz
+ kiilerin sadece dilediiniz sayfalar覺 g繹r羹nt羹lemesini
+ salayabilirsiniz.</p>
+
+ <p>Bu makale sitenizin baz覺 par癟alar覺n覺 korumak i癟in kullanaca覺n覺z
+ "standart" yollar覺 i癟ermektedir.</p>
+
+ <div class="note"><h3>Bilginize:</h3>
+ <p>Eer bilgileriniz ger癟ekten gizlilie ihtiya癟 duyuyorsa kimlik
+ dorulamas覺na ilaveten <code class="module"><a href="../mod/mod_ssl.html">mod_ssl</a></code> mod羹l羹n羹 de
+ kullanabilirsiniz.</p>
+ </div>
+
+ </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="theprerequisites" id="theprerequisites">n gereksinimler</a></h2>
+
+ <p>Bu makalede bahsi ge癟en y繹nergeler ya ana sunucu yap覺land覺rma
+ dosyas覺nda (genellikle <code class="directive"><a href="../mod/core.html#directory">&lt;Directory&gt;</a></code> b繹l羹m羹nde) ya da dizin i癟i
+ yap覺land覺rma dosyalar覺nda (<code>.htaccess</code> dosyalar覺)
+ bulunmak zorundad覺r.</p>
+
+ <p>Eer <code>.htaccess</code> dosyalar覺n覺 kullanmay覺
+ tasarl覺yorsan覺z, kimlik dorulama y繹nergelerine bu dosyalar覺n i癟ine
+ koymaya izin veren sunucu yap覺land覺rmas覺na ihtiyac覺n覺z olacakt覺r.
+ Bunun i癟in, dizin i癟i yap覺land覺rma dosyalar覺n覺n i癟ine hangi
+ y繹nergelerin konaca覺n覺 belirleyen <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code> y繹nergesi kullan覺l覺r.</p>
+
+ <p>Kimlik dorulamadan s繹zettiimize g繹re, aa覺da g繹sterilen
+ ekilde bir <code class="directive"><a href="../mod/core.html#allowoverride">AllowOverride</a></code> y繹nergesine ihtiyac覺n覺z olacakt覺r:</p>
+
+ <pre class="prettyprint lang-config">AllowOverride AuthConfig</pre>
+
+
+ <p>Y繹nergeleri dorudan ana sunucunun yap覺land覺rma dosyas覺na
+ koyacaksan覺z bu dosyaya yazma izniniz olmal覺d覺r.</p>
+
+ <p>Baz覺 dosyalar覺n nerede sakland覺覺n覺 bilmek i癟in sunucunun dizin
+ yap覺s覺 hakk覺nda biraz bilgi sahibi olman覺z gerekmektedir. Bu 癟ok da
+ zor olmamakla birlikte bu noktaya gelindiinde konuyu
+ netletireceiz.</p>
+
+ <p>Ayr覺ca <code class="module"><a href="../mod/mod_authn_core.html">mod_authn_core</a></code> ve
+ <code class="module"><a href="../mod/mod_authz_core.html">mod_authz_core</a></code> mod羹lleri ya <code>httpd</code>
+ 癟al覺t覺r覺labilirinin i癟inde derlenmi olmal覺 ya da
+ <code>httpd.conf</code> yap覺land覺rma dosyas覺 ile y羹klenmelidir. Bu
+ iki mod羹l HTTP sunucusunda kimlik dorulama ve yetkilendirme
+ kullan覺m覺 ve yap覺land覺rmas覺 i癟in b羹y羹k 繹neme sahip temel y繹nergeleri
+ ve ilevsellii salar.</p>
+
+ </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="gettingitworking" id="gettingitworking">al覺maya Balama</a></h2>
+ <p>Burada, sunucu 羹zerindeki bir dizini parolayla korumak i癟in
+ gereken temel bilgiler verilecektir.</p>
+
+ <p>襤lk olarak bir parola dosyas覺 oluturmal覺s覺n覺z. Bunu nas覺l
+ yapaca覺n覺z, 繹zellikle, se癟tiiniz kimlik dorulay覺c覺ya g繹re
+ deiiklik g繹sterir. Bunun 羹zerinde ileride daha fazla duraca覺z.
+ Balang覺癟 i癟in parolalar覺 bir metin dosyas覺nda tutaca覺z.</p>
+
+ <p>Bu dosya belge k繹k dizini alt覺nda olmamal覺d覺r. B繹ylece bakalar覺
+ parola dosyas覺n覺 indiremezler. rnein belgeleriniz
+ <code>/usr/local/apache/htdocs</code> 羹zerinden sunuluyorsa parola
+ dosyan覺z覺 <code>/usr/local/apache/passwd</code> dizininde
+ tutabilirsiniz.</p>
+
+ <p>Dosyay覺 oluturmak i癟in Apache ile gelen
+ <code class="program"><a href="../programs/htpasswd.html">htpasswd</a></code> uygulamas覺n覺 kullanaca覺z. Bu uygulama
+ Apache'nin kurulumunda belirtilen <code>bin</code> dizininde
+ bulunur. Eer Apache'yi 羹癟羹nc羹 parti paketlerden kurduysan覺z,
+ 癟al覺t覺r覺labilir dosyalar覺n bulunduu yollar 羹zerinde olmal覺d覺r.</p>
+
+ <p>Bir dosya oluturmak i癟in unlar覺 yaz覺n:</p>
+
+ <div class="example"><p><code>
+ htpasswd -c /usr/local/apache/passwd/passwords umut
+ </code></p></div>
+
+ <p><code class="program"><a href="../programs/htpasswd.html">htpasswd</a></code> size parola soracakt覺r arkas覺ndan da
+ teyit etmek i癟in parolay覺 tekrar girmenizi isteyecektir:</p>
+
+ <div class="example"><p><code>
+ # htpasswd -c /usr/local/apache/passwd/passwords umut<br />
+ New password: parolam<br />
+ Re-type new password: parolam<br />
+ Adding password for user umut
+ </code></p></div>
+
+ <p>Eer <code class="program"><a href="../programs/htpasswd.html">htpasswd</a></code> normal yollar 羹zerinde deilse
+ 癟al覺t覺rmak i癟in dosyan覺n bulunduu tam yeri belirtmeniz
+ gerekecektir. Dosyan覺n 繹ntan覺ml覺 kurulum yeri:
+ <code>/usr/local/apache2/bin/htpasswd</code></p>
+
+ <p>Bundan sonra, sunucuyu, parola sormas覺 i癟in ve kimlerin eriim
+ izni olaca覺n覺 belirlemek i癟in yap覺land覺racaks覺n覺z. Bu ilemi
+ <code>httpd.conf</code>dosyas覺n覺 d羹zenleyerek ya da bir
+ <code>.htaccess</code> dosyas覺 kullanarak yapabilirsiniz. rnein,
+ <code>/usr/local/apache/htdocs/secret</code> dizinini korumay覺
+ ama癟l覺yorsan覺z, u y繹nergeleri kullanabilirsiniz. Bu y繹nergeleri
+ <code>/usr/local/apache/htdocs/secret/.htaccess</code> dosyas覺 i癟ine
+ veya <code>httpd.conf</code> i癟indeki &lt;Directory
+ "/usr/local/apache/htdocs/secret"&gt; b繹l羹m羹ne koyabilirsiniz.</p>
+
+ <pre class="prettyprint lang-config">AuthType Basic
+AuthName "Gizli Dosyalar"
+# (Aa覺daki sat覺r覺n kullan覺m覺 istee bal覺d覺r)
+AuthBasicProvider file
+AuthUserFile "/usr/local/apache/passwd/passwords"
+Require user umut</pre>
+
+
+ <p>Bu y繹nergeleri tek tek inceleyelim.
+ <code class="directive"><a href="../mod/mod_authn_core.html#authtype">AuthType</a></code> y繹nergesi
+ kullan覺c覺n覺n kimliini dorulamakta kullan覺lacak y繹ntemi se癟er. En
+ 癟ok kullan覺lan y繹ntem <code>Basic</code>'tir ve bu y繹ntem
+ <code class="module"><a href="../mod/mod_auth_basic.html">mod_auth_basic</a></code> mod羹l羹yle ger癟eklenmitir. Temel
+ (<code>Basic</code>) kimlik dorulamas覺yla g繹nderilen parolan覺n
+ ifrelenmeyeceini unutmay覺n. Bu y繹ntem, bu sebepten dolay覺
+ <code class="module"><a href="../mod/mod_ssl.html">mod_ssl</a></code> eliinde kullan覺lmad覺覺 s羹rece y羹ksek
+ hassasiyete sahip bilgiler i癟in kullan覺lmamal覺d覺r. Apache bir baka
+ kimlik dorulama y繹ntemini daha destekler: <code>AuthType
+ Digest</code>. Bu y繹ntem <code class="module"><a href="../mod/mod_auth_digest.html">mod_auth_digest</a></code> taraf覺ndan
+ ger癟eklenmiti ve 癟ok daha g羹venli olaca覺 d羹羹n羹lm羹t羹. Bu art覺k
+ ge癟erliliini yitirdiinden balant覺n覺n bundan b繹yle
+ <code class="module"><a href="../mod/mod_ssl.html">mod_ssl</a></code> ile ifrelenmesi gerekmektedir.</p>
+
+ <p><code class="directive"><a href="../mod/mod_authn_core.html#authname">AuthName</a></code> y繹nergesi
+ ile kimlik dorulamada kullan覺lacak <dfn>Saha</dfn> da
+ belirtilebilir. Saha kullan覺m覺n覺n, bal覺ca iki ilevi vard覺r.
+ Birincisi, istemci s覺kl覺kla bu bilgiyi kullan覺c覺ya parola diyalog
+ kutusunun bir par癟as覺 olarak sunar. 襤kincisi, belirtilen kimlik
+ dorulamal覺 alan i癟in g繹nderilecek parolay覺 belirlerken istemci
+ taraf覺ndan kullan覺l覺r.</p>
+
+ <p>rnein, bir istemcinin <code>"Gizli Dosyalar"</code> alan覺nda
+ kimlii dorulanm覺 olsun. Ayn覺 sunucu 羹zerinde <code>"Gizli
+ Dosyalar"</code> Sahas覺 olarak belirlenmi alanlarda ayn覺 parola
+ 繹zdevinimli olarak yinelenecektir. B繹ylece parola bir kere girilerek
+ ayn覺 Sahay覺 paylaan 癟ok say覺da k覺s覺tlanm覺 alana ula覺rken oluacak
+ gecikmeden kullan覺c覺 korunmu olur. G羹venlik gerek癟elerinden dolay覺,
+ her sunucu ad覺 deitiriliinde istemcinin parolay覺 yeniden sormas覺
+ gerekir.</p>
+
+ <p><code class="directive"><a href="../mod/mod_auth_basic.html#authbasicprovider">AuthBasicProvider</a></code>
+ y繹nergesinin 繹ntan覺ml覺 deeri <code>file</code> olduundan, bu
+ durumda, bu y繹nergenin kullan覺m覺 istee bal覺d覺r. Ancak, eer kimlik
+ dorulamas覺 i癟in <code class="module"><a href="../mod/mod_authn_dbm.html">mod_authn_dbm</a></code> ya da
+ <code class="module"><a href="../mod/mod_authn_dbd.html">mod_authn_dbd</a></code> gibi farkl覺 bir kaynak se癟ecekseniz
+ bu y繹nergeyi kullanman覺z gerekecektir.</p>
+
+ <p><code class="directive"><a href="../mod/mod_authn_file.html#authuserfile">AuthUserFile</a></code>
+ y繹nergesi <code class="program"><a href="../programs/htpasswd.html">htpasswd</a></code> ile oluturduumuz parola
+ dosyas覺n覺n yerini belirtmek i癟in kullan覺l覺r. Eer 癟ok say覺da
+ kullan覺c覺n覺z varsa her bir kullan覺c覺y覺 her kimlik dorulama istei
+ i癟in kimlik bilgilerini bir metin dosyas覺nda aramak gayet yava
+ olacakt覺r. Apache, kullan覺c覺 bilgilerini h覺zl覺 bir veritaban覺
+ dosyas覺nda depolama 繹zelliine de sahiptir. Bu ama癟la,
+ <code class="module"><a href="../mod/mod_authn_dbm.html">mod_authn_dbm</a></code> mod羹l羹n羹n
+ <code class="directive"><a href="../mod/mod_authn_dbm.html#authdbmuserfile">AuthDBMUserFile</a></code>
+ y繹nergesi kullan覺labilir. Bu dosyalar <code class="program"><a href="../programs/dbmmanage.html">dbmmanage</a></code> ve
+ <code class="program"><a href="../programs/htdbm.html">htdbm</a></code> program覺 ile oluturulabilir ve deitirilebilir.
+ 癟羹nc羹 parti mod羹llerinde 癟ok say覺da
+ baka kimlik dorulama t羹r羹 de vard覺r.</p>
+
+ <p>Son olarak <code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code>
+ y繹nergesi, sunucunun bu b繹lgesine eriimine izin verilen
+ kullan覺c覺lar覺 ayarlama ileminin kimlik dorulamas覺yla ilgili
+ k覺sm覺n覺 salar. Bir sonraki b繹l羹mde <code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code> y繹nergesini kullanman覺n
+ 癟eitli yolar覺 羹zerinde duraca覺z.</p>
+ </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="lettingmorethanonepersonin" id="lettingmorethanonepersonin">Birden 癟ok kiiye izin vermek</a></h2>
+
+ <p>Yukar覺daki y繹nergelerle bir dizinde sadece bir kiiye
+ (<code>umut</code> adl覺 kullan覺c覺ya) izin verir. ounlukla birden
+ 癟ok kiiye izin verilmesi istenir. Bu durumda <code class="directive"><a href="../mod/mod_authz_groupfile.html#authgroupfile">AuthGroupFile</a></code> y繹nergesi
+ devreye girer.</p>
+
+ <p>Eer birden 癟ok kiiye izin vermek istiyorsan覺z i癟inde kullan覺c覺
+ isimlerinin olduu bir grup dosyas覺 oluturmal覺s覺n覺z. Bu dosyan覺n
+ bi癟emi gayet basittir ve bunu herhangi bir metin d羹zenleyici ile
+ oluturabilirsiniz. Bu dosyan覺n i癟erii aa覺daki gibi
+ g繹r羹necektir:</p>
+
+ <div class="example"><p><code>
+ GroupName: umut samet engin kubilay
+ </code></p></div>
+
+ <p>Dosya, sadece, boluklarla birbirinden ayr覺lm覺 gurup 羹yelerinin
+ isimlerinden oluan uzun bir liste i癟erir.</p>
+
+ <p>Varolan parola dosyas覺na bir kullan覺c覺 eklemek i癟in unu
+ yaz覺n:</p>
+
+ <div class="example"><p><code>
+ htpasswd /usr/local/apache/passwd/passwords birey
+ </code></p></div>
+
+ <p>Evvelce alm覺 olduunuz yan覺t覺 yine alacaks覺n覺z ama bu sefer yeni
+ bir dosya oluturulmak yerine var olan bir dosyaya eklenecektir.
+ (Yeni bir parola dosyas覺 oluturmak i癟in <code>-c</code> se癟enei
+ kullan覺l覺r).</p>
+
+ <p>imdi, <code>.htaccess</code> dosyan覺z覺 veya
+ <code class="directive"><a href="../mod/core.html#directory">&lt;Directory&gt;</a></code> b繹l羹m羹n羹z羹
+ aa覺da g繹r羹ld羹羹 ekilde deitirebilirsiniz:</p>
+
+ <pre class="prettyprint lang-config">AuthType Basic
+AuthName "Davete Binaen"
+# Sat覺r istee bal覺d覺r:
+AuthBasicProvider file
+AuthUserFile "/usr/local/apache/passwd/passwords"
+AuthGroupFile "/usr/local/apache/passwd/groups"
+Require group Grupismi</pre>
+
+
+ <p>Art覺k, <code>Grupismi</code> gurubunda listelenmi ve
+ <code>password</code> dosyas覺nda kayd覺 olan kiiye, parolay覺 doru
+ yazd覺覺 takdirde izin verilecektir.</p>
+
+ <p>oklu kullan覺c覺ya izin veren biraz daha az kullan覺lan baka bir
+ yol daha mevcuttur. Bir gurup dosyas覺 oluturmaktansa, u y繹nergeyi
+ kullanabilirsiniz:</p>
+
+ <pre class="prettyprint lang-config">Require valid-user</pre>
+
+
+ <p><code>Require user umut</code> sat覺r覺 ile parola dosyas覺nda
+ listelenmi ve parolay覺 doru olarak giren herhangi bir kiiye izin
+ vermektense, her grup i癟in ayr覺 bir parola dosyas覺 tutarak grup
+ davran覺覺n覺 taklit edebilirsiniz.</p>
+
+ </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="possibleproblems" id="possibleproblems">Olas覺 Sorunlar</a></h2>
+ <p>Temel kimlik dorulama yolu belirtildii i癟in, sunucuya
+ yapt覺覺n覺z her belge istediinde kullan覺c覺 ad覺n覺z覺n ve parolan覺z覺n
+ dorulanmas覺 gerekir. Hatta ayn覺 sayfay覺 yeniden y羹klerken ya da
+ sayfadaki her bir resim i癟in bu yap覺lmal覺d覺r (ayet korunmakta olan
+ bir dizinden geliyorsa). Bu ilem h覺z覺 azaltacakt覺r. Yavalama
+ miktar覺 parola dosyan覺z覺n b羹y羹kl羹羹 ile orant覺l覺 olacakt覺r, 癟羹nk羹 bu
+ ilem s覺ras覺nda dosya a癟覺lacak ve kullan覺c覺lar覺n aras覺nda isminiz
+ bulunana kadar liste aa覺 doru taranacakt覺r. Bu ilem sayfa her
+ y羹kleniinde tekrar edilecektir.</p>
+
+ <p>Buradan 癟覺kacak sonu癟, bir parola dosyas覺na konulan kullan覺c覺
+ say覺s覺nda bir 羹st s覺n覺r olmas覺 gerekliliidir. Bu s覺n覺r sunucunuzun
+ baar覺m覺na bal覺 olarak deiiklik g繹sterir. Bir ka癟 y羹z kay覺t覺n
+ 羹st羹nde giri yapt覺覺n覺zda h覺z d羹羹羹n羹 g繹zlemlebilirsiniz 襤te bu
+ anda kimlik dorulama i癟in baka bir y繹ntem aramaya balars覺n覺z.</p>
+
+ </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="dbmdbd" id="dbmdbd">Dier parola depolama y繹ntemleri</a></h2>
+
+ <p>Parolalar覺 basit bir metin dosyas覺nda depolamak yukar覺da
+ bahsedilen sorunlara yol a癟t覺覺ndan parolalar覺 baka bir yerde
+ depolamay覺 d羹羹nebilirsiniz; 繹rnein bir veritaban覺nda.</p>
+
+ <p><code class="module"><a href="../mod/mod_authn_dbm.html">mod_authn_dbm</a></code> ve <code class="module"><a href="../mod/mod_authn_dbd.html">mod_authn_dbd</a></code>
+ mod羹lleri bunu m羹mk羹n k覺lan iki mod羹ld羹r. Depolama y繹nemi olarak
+ <code><code class="directive"><a href="../mod/mod_auth_basic.html#authbasicprovider">AuthBasicProvider</a></code> file</code> yerine, <code>dbm</code>
+ veya <code>dbd</code> kullanabilirsiniz.</p>
+
+ <p>Bir metin dosyas覺 yerine bir dbm dosyas覺 kullan覺m 繹rnei:</p>
+
+ <pre class="prettyprint lang-config">&lt;Directory "/www/docs/private"&gt;
+ AuthName "Private"
+ AuthType Basic
+ AuthBasicProvider dbm
+ AuthDBMUserFile "/www/passwords/passwd.dbm"
+ Require valid-user
+&lt;/Directory&gt;</pre>
+
+
+ <p>Baka se癟enekler de m羹mk羹nd羹r. Ayr覺n覺lar i癟in
+ <code class="module"><a href="../mod/mod_authn_dbm.html">mod_authn_dbm</a></code> belgesine bavurun.</p>
+
+ </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="multprovider" id="multprovider">Birden 癟ok tedarik癟i kullanmak</a></h2>
+
+ <p>Kimlik dorulama ve yetkilendirme mimarisine dayal覺 yeni
+ tedarik癟iyi kullanarak tek bir yetkilendirme ya da kimlik dorulama
+ y繹ntemine kilitlenip kalmayacaks覺n覺z. Asl覺nda birden 癟ok tedarik癟i
+ ihtiyac覺n覺za cevap vermek i癟in bir arada kullan覺labilir. Aa覺daki
+ 繹rnekte dosya ve LDAP tabanl覺 kimlik dorulama tedarik癟ileri bir
+ arada kullan覺lm覺t覺r.</p>
+
+ <pre class="prettyprint lang-config">&lt;Directory "/www/docs/private"&gt;
+ AuthName "Private"
+ AuthType Basic
+ AuthBasicProvider file ldap
+ AuthUserFile "/usr/local/apache/passwd/passwords"
+ AuthLDAPURL ldap://ldaphost/o=yourorg
+ Require valid-user
+&lt;/Directory&gt;</pre>
+
+
+ <p>Bu 繹rnekte dosya tedarik癟isi, ilk olarak kullan覺c覺n覺n kimliini
+ dorulamaya teebb羹s edecektir. Kullan覺c覺n覺n kimlii
+ dorulanam覺yorsa LDAP tedarik癟isi 癟a覺r覺l覺r. Eer kurumunuz birden
+ 癟ok kimlik dorulama tedarik癟isini y羹r羹rl羹e koyuyorsa bu, kimlik
+ dorulama faaliyet alan覺n覺n geniletilmesini salar. Dier kimlik
+ kan覺tlama ve yetkilendirme senaryolar覺 tek bir kimlik dorulamas覺
+ ile birden fazla yetkilendirme t羹r羹ne izin verebilir.</p>
+
+ <p>ok say覺da kimlik dorulama tedarik癟isi uygulamaya konulabilecei
+ gibi, 癟ok say覺da yetkilendirme y繹ntemi de kullan覺labilir. Bu 繹rnekte
+ dosya i癟in hem dosyal覺 hem de LDAP grup kimlik dorulamas覺
+ kullan覺lm覺t覺r.</p>
+
+ <pre class="prettyprint lang-config">&lt;Directory "/www/docs/private"&gt;
+ AuthName "Private"
+ AuthType Basic
+ AuthBasicProvider file
+ AuthUserFile "/usr/local/apache/passwd/passwords"
+ AuthLDAPURL ldap://ldaphost/o=yourorg
+ AuthGroupFile "/usr/local/apache/passwd/groups"
+ Require group GroupName
+ Require ldap-group cn=mygroup,o=yourorg
+&lt;/Directory&gt;</pre>
+
+
+ <p>Kimlik dorulama konusunu biraz daha geniletirsek, <code class="directive"><a href="../mod/mod_authz_core.html#requireall">&lt;RequireAll&gt;</a></code> ve
+ <code class="directive"><a href="../mod/mod_authz_core.html#requireany">&lt;RequireAny&gt;</a></code> gibi yetkilendirme ta覺y覺c覺s覺
+ y繹nergelerle hangi iznin hangi s覺rayla uygulanaca覺n覺
+ belirlenebilir. <a href="../mod/mod_authz_core.html#logic">Yetkilendirme Ta覺y覺c覺lar覺</a> b繹l羹m羹nde bunun bir uygulama
+ 繹rneini g繹rebilirsiniz.</p>
+
+ </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="beyond" id="beyond">Yetkilendirmenin biraz 繹tesi</a></h2>
+ <p>Tek bir veri deposundan yap覺lacak tek bir s覺namadan 癟ok daha
+ esnek kimlik dorulamas覺 yap覺labilir. S覺ralama, mant覺k ve hangi
+ kimlik dorulamas覺n覺n kullan覺laca覺n覺 se癟mek m羹mk羹nd羹r.</p>
+
+ <h3><a name="authandororder" id="authandororder">Mant覺k ve s覺ralaman覺n uygulanmas覺</a></h3>
+
+ <p>Yetkilendirmenin hangi s覺rayla uygulanaca覺 ve nas覺l
+ denetlenecei ge癟mite biraz gizemli bir konuydu. Apache 2.2'de,
+ tedarik癟i tabanl覺 kimlik dorulamas覺n覺n devreye girmesiyle as覺l
+ kimlik dorulama ilemini yetkilendirme ve destek ilevselliinden
+ ay覺rmak m羹mk羹n oldu. Bunun faydalar覺ndan birisi de kimlik
+ dorulama tedarik癟ilerinin yap覺land覺r覺labilmesi ve auth mod羹l羹n羹n
+ kendi y羹kleme s覺ras覺ndan ba覺ms覺z olarak 繹zel bir s覺rayla
+ 癟ar覺labilmesidir. Bu tedarik癟i tabanl覺 mekanizman覺n ayn覺s覺
+ yetkilendirmeye de getirilmitir. Bunun anlam覺 <code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code> y繹nergesinde hangi
+ izin y繹nteminin kullan覺lmas覺 gerektiinin belirtmesinin yan覺nda
+ hangi s覺rayla 癟a覺r覺lacaklar覺n覺n da belirlenebildiidir. ok
+ say覺da yetkilendirme y繹ntemi kullan覺ld覺覺nda, bunlar, <code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code> y繹nergelerinin
+ yap覺land覺rma dosyas覺nda g繹r羹nd羹kleri s覺ra ile 癟a覺r覺l覺r.</p>
+
+ <p><code class="directive"><a href="../mod/mod_authz_core.html#requireall">&lt;RequireAll&gt;</a></code> ve <code class="directive"><a href="../mod/mod_authz_core.html#requireany">&lt;RequireAny&gt;</a></code> gibi yetkilendirme
+ ta覺y覺c覺s覺 y繹nergelerin devreye girmesiyle yetkilendirme
+ y繹ntemlerinin ne zaman 癟a覺r覺laca覺 ve 癟a覺r覺ld覺覺nda ve eriime
+ izin verirken hangi kurallar覺n uygulanaca覺 konusunda denetim
+ yap覺land覺rman覺n eline ge癟mektedir. Karma覺k yetkilendime mant覺覺n覺
+ ifade etmek i癟in kullan覺lan bir 繹rnei g繹rmek i癟in
+ <a href="../mod/mod_authz_core.html#logic">Yetkilendirme
+ Ta覺y覺c覺lar覺</a> b繹l羹m羹ne bak覺n覺z.</p>
+
+ <p>ntan覺ml覺 olarak t羹m <code class="directive"><a href="../mod/mod_authz_core.html#require">
+ Require</a></code> y繹nergeleri, <code class="directive"><a href="../mod/mod_authz_core.html#requireany">&lt;RequireAny&gt;</a></code>
+ ta覺y覺c覺 y繹nergesinin i癟ine konur. Baka bir deyile eer
+ belirtilen kimlik dorulama y繹ntemlerinden herhangi biri baar覺l覺
+ olursa yetkilendirme de salanm覺 olur.</p>
+
+
+
+ <h3><a name="reqaccessctrl" id="reqaccessctrl">Eriim denetimi i癟in yetkilendirme tedarik癟ilerinin
+ kullan覺m覺</a></h3>
+
+ <p>Kullan覺c覺 ad覺 ve parolas覺na g繹re kimlik dorulama hikayenin
+ sadece bir b繹l羹m羹d羹r. S覺kl覺kla insanlara kim olduklar覺na g繹re
+ deil bireylere dayanarak izin vermek istersiniz. rnein nereden
+ geldikleri gibi.</p>
+
+ <p><code>all</code>, <code>env</code>, <code>host</code> ve
+ <code>ip</code> gibi yetkilendirme tedarik癟ileri ile, bir belgenin
+ istendii makinenin IP adresi veya konak ismi gibi baz覺 繹zelliklerine
+ dayal覺 olarak eriime izin verip vermeyeceinizi belirtebilirsiniz.</p>
+
+ <p>Bu tedarik癟ilerin kullan覺m覺 <code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code> y繹nergesinde a癟覺klanm覺t覺r. Bu y繹nergeler,
+ isteklerin ilenmesi s覺ras覺nda yetkilendirme aamas覺nda
+ 癟a覺r覺lacak yetkilendirme tedarik癟ilerini kayda ge癟irir. rnein:
+ </p>
+
+ <pre class="prettyprint lang-config">Require ip <var>adres</var>
+ </pre>
+
+
+ <p>Burada, <var>adres</var> bir IP adresidir (veya k覺smi bir IP
+ addresidir)</p>
+
+ <pre class="prettyprint lang-config">Require host <var>alan_ad覺</var>
+ </pre>
+
+
+ <p>Burada, <var>alan_ad覺</var> bir tam nitelikli alan ad覺d覺r
+ (ya da k覺smi alan ad覺d覺r); gerekirse 癟ok say覺da alan ad覺 veya IP
+ adresi de belirtilebilir.</p>
+
+ <p>rnein, yorum alan覺n覺 gereksiz iletilerle dolduran birini uzak
+ tutmak istediinizi varsayal覺m. Bu kiiyi uzak tutmak i癟in unlar覺
+ yapabilirsiniz:</p>
+
+ <pre class="prettyprint lang-config">&lt;RequireAll&gt;
+ Require all granted
+ Require not ip 10.252.46.165
+&lt;/RequireAll&gt;</pre>
+
+
+ <p>Bu adresden gelen ziyaret癟iler bu y繹nergedeki i癟erii
+ g繹remeyeceklerdir. Bunun yerine, elinizde IP adresi deil de
+ makine ad覺 varsa unu kullanabilirsiniz:</p>
+
+ <pre class="prettyprint lang-config">&lt;RequireAll&gt;
+ Require all granted
+ Require not host host.example.com
+&lt;/RequireAll&gt;</pre>
+
+
+ <p>Eer alan ad覺n覺n taman覺dan gelecek olan b羹t羹n eriimleri
+ engellemek isterseniz adresin ya da alan ad覺n覺n bir par癟as覺n覺
+ belirtin:</p>
+
+ <pre class="prettyprint lang-config">&lt;RequireAll&gt;
+ Require all granted
+ Require not ip 192.168.205
+ Require not host phishers.example.com moreidiots.example
+ Require not host ke
+&lt;/RequireAll&gt;</pre>
+
+
+ <p><code class="directive"><a href="../mod/mod_authz_core.html#requireall">&lt;RequireAll&gt;</a></code> y繹nergesini 癟ok say覺da
+ <code class="directive"><a href="../mod/mod_authz_core.html#require">&lt;Require&gt;</a></code> y繹nergesi ile birlikte kullanarak,
+ sadece <code>not</code> ile olumsuzlanan t羹m koullar覺 ger癟ekleyen
+ balant覺lara eriim verilir. Baka bir deyile, olumsuzlanan koullar覺
+ ger癟eklemeyen balant覺lar覺n eriimi engellenir.</p>
+
+
+
+ <h3><a name="filesystem" id="filesystem">Eriim denetimi ve geriye uyumluluk</a></h3>
+
+ <p>Kimlik dorulama i癟in tedarik tabanl覺 mekanizma kullan覺m覺n覺n
+ yan etkilerinden birisi,
+ <code class="directive"><a href="../mod/mod_access_compat.html#order">Order</a></code>,
+ <code class="directive"><a href="../mod/mod_access_compat.html#allow">Allow</a></code>,
+ <code class="directive"><a href="../mod/mod_access_compat.html#deny">Deny</a></code> ve
+ <code class="directive"><a href="../mod/mod_access_compat.html#satisfy">Satisfy</a></code> eriim
+ denetim y繹nergelerine art覺k ihtiya癟 duyulmamas覺d覺r. Ancak eski
+ yap覺land覺rmalarla uyumluluu salamak i癟in bu y繹nergeler
+ <code class="module"><a href="../mod/mod_access_compat.html">mod_access_compat</a></code> mod羹l羹ne ta覺nm覺t覺r.</p>
+
+ <div class="warning"><h3>Note</h3>
+ <p><code class="module"><a href="../mod/mod_access_compat.html">mod_access_compat</a></code> ile salanan y繹nergelerin
+ kullan覺m覺 art覺k 繹nerilmemekte, <code class="module"><a href="../mod/mod_authz_host.html">mod_authz_host</a></code>
+ mod羹l羹ndeki y繹nergeler 繹nerilmektedir. <code class="directive"><a href="../mod/mod_access_compat.html#order">Order</a></code>, <code class="directive"><a href="../mod/mod_access_compat.html#allow">Allow</a></code> veya <code class="directive"><a href="../mod/mod_access_compat.html#deny">Deny</a></code> ile
+ <code class="directive"><a href="../mod/mod_authz_core.html#require">Require</a></code> gibi daha yeni
+ olanlar覺n覺n yenilerle kar覺覺k kullan覺m覺 teknik olarak m羹mk羹nse de
+ 繹nerilmemektedir. <code class="module"><a href="../mod/mod_access_compat.html">mod_access_compat</a></code> mod羹l羹, 2.4
+ y羹kseltmesini kolaylat覺rmak i癟in sadece eski y繹nergeleri i癟eren
+ yap覺land覺rmalar覺 desteklemek 羹zere oluturulmutur. Daha ayr覺nt覺l覺
+ bilgi i癟in <a href="../upgrading.html">y羹kseltme</a> belgesine bak覺n覺z.
+ </p>
+ </div>
+
+
+ </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="socache" id="socache">Kimlik Dorulama Arabellei</a></h2>
+ <p>Zaman zaman kimlik dorulama a覺n覺zda veya salay覺c覺(lar覺)n覺zda kabul
+ edilemez y羹kler oluturur. Bu 癟ounlukla <code class="module"><a href="../mod/mod_authn_dbd.html">mod_authn_dbd</a></code>
+ (veya 羹癟羹nc羹 parti/繹zel salay覺c覺lar覺n) kullan覺c覺lar覺n覺 etkiler. Bununla
+ ilgilenmek i癟in httpd 2.3/2.4, kimlik bilgilerini arabelleklemek ve 繹zg羹n
+ salay覺c覺lar覺n y羹klerini azaltmak i癟in yeni bir arabellekleme salay覺c覺s覺
+ olarak <code class="module"><a href="../mod/mod_authn_socache.html">mod_authn_socache</a></code> mod羹l羹 ile gelmektedir.</p>
+ <p>Bu, baz覺 kullan覺c覺lar i癟in 繹nemli bir baar覺m art覺覺 salayabilir.</p>
+ </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="moreinformation" id="moreinformation">Daha fazla bilgi</a></h2>
+ <p>Daha fazla bilgi i癟in <code class="module"><a href="../mod/mod_auth_basic.html">mod_auth_basic</a></code> ve
+ <code class="module"><a href="../mod/mod_authz_host.html">mod_authz_host</a></code> mod羹llerinin belgelerine bak覺n覺z.
+ <code class="directive"><a href="../mod/mod_authn_core.html#authnprovideralias">AuthnProviderAlias</a></code>
+ y繹nergesi ile baz覺 yap覺land覺rmalar覺n覺z覺 basitletirebilirsiniz.</p>
+
+ <p>Apache taraf覺ndan desteklenen ifrelerle ilgili bilgi i癟in <a href="../misc/password_encryptions.html">Parola Bi癟emleri</a>
+ belgesine bak覺n覺z.</p>
+
+ <p><a href="access.html">Eriim Denetimi</a> nas覺l belgesinden de
+ baz覺 bilgiler edinebilirsiniz.</p>
+ </div></div>
+<div class="bottomlang">
+<p><span>Mevcut Diller: </span><a href="../en/howto/auth.html" hreflang="en" rel="alternate" title="English">&nbsp;en&nbsp;</a> |
+<a href="../es/howto/auth.html" hreflang="es" rel="alternate" title="Espa簽ol">&nbsp;es&nbsp;</a> |
+<a href="../fr/howto/auth.html" hreflang="fr" rel="alternate" title="Fran癟ais">&nbsp;fr&nbsp;</a> |
+<a href="../ja/howto/auth.html" hreflang="ja" rel="alternate" title="Japanese">&nbsp;ja&nbsp;</a> |
+<a href="../ko/howto/auth.html" hreflang="ko" rel="alternate" title="Korean">&nbsp;ko&nbsp;</a> |
+<a href="../tr/howto/auth.html" title="T羹rk癟e">&nbsp;tr&nbsp;</a></p>
+</div><div class="top"><a href="#page-header"><img src="../images/up.gif" alt="top" /></a></div><div class="section"><h2><a id="comments_section" name="comments_section">Yorumlar</a></h2><div class="warning"><strong>Notice:</strong><br />This is not a Q&amp;A section. Comments placed here should be pointed towards suggestions on improving the documentation or server, and may be removed by our moderators if they are either implemented or considered invalid/off-topic. Questions on how to manage the Apache HTTP Server should be directed at either our IRC channel, #httpd, on Libera.chat, or sent to our <a href="https://httpd.apache.org/lists.html">mailing lists</a>.</div>
+<script type="text/javascript"><!--//--><![CDATA[//><!--
+var comments_shortname = 'httpd';
+var comments_identifier = 'http://httpd.apache.org/docs/2.4/howto/auth.html';
+(function(w, d) {
+ if (w.location.hostname.toLowerCase() == "httpd.apache.org") {
+ d.write('<div id="comments_thread"><\/div>');
+ var s = d.createElement('script');
+ s.type = 'text/javascript';
+ s.async = true;
+ s.src = 'https://comments.apache.org/show_comments.lua?site=' + comments_shortname + '&page=' + comments_identifier;
+ (d.getElementsByTagName('head')[0] || d.getElementsByTagName('body')[0]).appendChild(s);
+ }
+ else {
+ d.write('<div id="comments_thread">Comments are disabled for this page at the moment.<\/div>');
+ }
+})(window, document);
+//--><!]]></script></div><div id="footer">
+<p class="apache">Copyright 2023 The Apache Software Foundation.<br /><a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a> alt覺nda lisansl覺d覺r.</p>
+<p class="menu"><a href="../mod/">Mod羹ller</a> | <a href="../mod/directives.html">Y繹nergeler</a> | <a href="http://wiki.apache.org/httpd/FAQ">SSS</a> | <a href="../glossary.html">Terimler</a> | <a href="../sitemap.html">Site Haritas覺</a></p></div><script type="text/javascript"><!--//--><![CDATA[//><!--
+if (typeof(prettyPrint) !== 'undefined') {
+ prettyPrint();
+}
+//--><!]]></script>
+</body></html> \ No newline at end of file