Minor polishing.

This commit is contained in:
Ben Alex 2004-12-25 07:18:17 +00:00
parent c77cb84f52
commit fe155223a1
2 changed files with 8 additions and 7 deletions

View File

@ -30,7 +30,7 @@
<h1>Frequently Asked Questions</h1> <h1>Frequently Asked Questions</h1>
<h2>What is Acegi Security?</h2> <h2>What is Acegi Security?</h2>
<p>Acegi Security is an open source project that provide comprehensive authentication <p>Acegi Security is an open source project that provides comprehensive authentication
and authorisation services for enterprise applications based on and authorisation services for enterprise applications based on
<a href="http://www.springframework.org">The Spring Framework</a>. <a href="http://www.springframework.org">The Spring Framework</a>.
Acegi Security can authenticate using a variety of pluggable providers, and Acegi Security can authenticate using a variety of pluggable providers, and
@ -69,7 +69,7 @@
expressed in the servlet specification's own limited URI path format. expressed in the servlet specification's own limited URI path format.
Acegi Security provides a far more comprehensive approach. For instance, Acegi Security provides a far more comprehensive approach. For instance,
you can use Ant paths or regular expressions, you can consider parts of the you can use Ant paths or regular expressions, you can consider parts of the
URI other than simply the requested page (eg you can consider request URI other than simply the requested page (eg you can consider HTTP GET
parameters), and you can implement your own runtime source of configuration parameters), and you can implement your own runtime source of configuration
data. This means your web request security can be dynamically changed during data. This means your web request security can be dynamically changed during
the actual execution of your webapp.<br><br></li> the actual execution of your webapp.<br><br></li>
@ -144,12 +144,12 @@
has a specific section on filter ordering.</p> has a specific section on filter ordering.</p>
<h2>I'm sure my filters are ordered correctly. What else could be wrong?</h2> <h2>I'm sure my filters are ordered correctly. What else could be wrong?</h2>
<p>The next most common source of problems step from custom <p>The next most common source of problems stem from custom
<code>AuthenticationDao</code> implementations that simply don't properly <code>AuthenticationDao</code> implementations that simply don't properly
implement the interface. For example, they return <code>null</code> instead implement the interface contract. For example, they return <code>null</code> instead
of the user not found exception, or fail to add in the of the user not found exception, or fail to add in the
<code>GrantedAuthority[]</code>s. Whilst <code>DaoAuthenticationProvider</code> <code>GrantedAuthority[]</code>s. Whilst <code>DaoAuthenticationProvider</code>
does its best to check the <code>AuthenticationDao</code>returns a valid does its best to check the <code>AuthenticationDao</code> returns a valid
<code>UserDetails</code>, we suggest you write the <code>UserDetails</code>, we suggest you write the
<code>UserDetails</code> object to the log and check it looks correct.</p> <code>UserDetails</code> object to the log and check it looks correct.</p>

View File

@ -25,7 +25,7 @@
href="http://apr.apache.org/versioning.html">Apache APR Project href="http://apr.apache.org/versioning.html">Apache APR Project
Versioning Guidelines</A> so you can identify backward Versioning Guidelines</A> so you can identify backward
compatibility.<BR><BR> compatibility.<BR><BR>
<LI><B>Fast results:</B> View our <a href="suggested.html">Suggested Steps</a> <LI><B>Fast results:</B> View our <a href="suggested.html">suggested steps</a>
for the fastest way to develop complex, security-compliant applications.<BR><BR> for the fastest way to develop complex, security-compliant applications.<BR><BR>
<LI><B>Enterprise-wide single sign on:</B> Using Yale University's open <LI><B>Enterprise-wide single sign on:</B> Using Yale University's open
source <A href="http://www.yale.edu/tp/auth/">Central Authentication source <A href="http://www.yale.edu/tp/auth/">Central Authentication
@ -151,7 +151,8 @@
using an open source security package leverages the continuous design using an open source security package leverages the continuous design
and code quality improvements that emerge from peer review.<BR><BR> and code quality improvements that emerge from peer review.<BR><BR>
<LI><B>Thorough documentation:</B> All APIs are fully documented using <LI><B>Thorough documentation:</B> All APIs are fully documented using
JavaDoc, with a 40+ page reference guide providing an easy-to-follow <a href="http://acegisecurity.sourceforge.net/multiproject/acegi-security/apidocs/index.html">JavaDoc</a>, with a 40+ page
<a href="reference.html">Reference Guide</a> providing an easy-to-follow
introduction. More documentation is provided on this web site, as introduction. More documentation is provided on this web site, as
shown in the left hand navigation sidebar.<BR><BR> shown in the left hand navigation sidebar.<BR><BR>
<LI><B>Apache license.</B><BR><BR></LI></UL><BR><B> <LI><B>Apache license.</B><BR><BR></LI></UL><BR><B>