📄 auth.html.en
字号:
<?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="en" xml:lang="en"><head><!-- XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX This file is generated from xml source: DO NOT EDIT XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX --><title>Authentication, Authorization and Access Control - Apache HTTP Server</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 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="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p><p class="apache">Apache HTTP Server Version 2.2</p><img alt="" src="../images/feather.gif" /></div><div class="up"><a href="./"><img title="<-" alt="<-" src="../images/left.gif" /></a></div><div id="path"><a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">HTTP Server</a> > <a href="http://httpd.apache.org/docs/">Documentation</a> > <a href="../">Version 2.2</a> > <a href="./">How-To / Tutorials</a></div><div id="page-content"><div id="preamble"><h1>Authentication, Authorization and Access Control</h1><div class="toplang"><p><span>Available Languages: </span><a href="../en/howto/auth.html" title="English"> en </a> |<a href="../ja/howto/auth.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> |<a href="../ko/howto/auth.html" hreflang="ko" rel="alternate" title="Korean"> ko </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></div><div id="quickview"><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 oneperson 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="#moreinformation">More information</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 andauthorization process. You will usually need to choose at least onemodule from each group.</p><ul> <li>Authentication type (see the <code class="directive"><a href="../mod/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 <ul> <li><code class="module"><a href="../mod/mod_authn_alias.html">mod_authn_alias</a></code></li> <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>Authorization (see the <code class="directive"><a href="../mod/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_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_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>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_authn_alias.html">mod_authn_alias</a></code> is not an authentication provider in itself, but allows other authentication providers to be configured in a flexible manner.</p> <p>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.</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"><Directory></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> <div class="example"><p><code> AllowOverride AuthConfig </code></p></div> <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></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 <Directory /usr/local/apache/apache/htdocs/secret> section.</p> <div class="example"><p><code> AuthType Basic<br /> AuthName "Restricted Files"<br />⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -