Minor polishing.
This commit is contained in:
parent
c77cb84f52
commit
fe155223a1
|
@ -30,7 +30,7 @@
|
|||
<h1>Frequently Asked Questions</h1>
|
||||
|
||||
<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
|
||||
<a href="http://www.springframework.org">The Spring Framework</a>.
|
||||
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.
|
||||
Acegi Security provides a far more comprehensive approach. For instance,
|
||||
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
|
||||
data. This means your web request security can be dynamically changed during
|
||||
the actual execution of your webapp.<br><br></li>
|
||||
|
@ -144,9 +144,9 @@
|
|||
has a specific section on filter ordering.</p>
|
||||
|
||||
<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
|
||||
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
|
||||
<code>GrantedAuthority[]</code>s. Whilst <code>DaoAuthenticationProvider</code>
|
||||
does its best to check the <code>AuthenticationDao</code> returns a valid
|
||||
|
|
|
@ -25,7 +25,7 @@
|
|||
href="http://apr.apache.org/versioning.html">Apache APR Project
|
||||
Versioning Guidelines</A> so you can identify backward
|
||||
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>
|
||||
<LI><B>Enterprise-wide single sign on:</B> Using Yale University's open
|
||||
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
|
||||
and code quality improvements that emerge from peer review.<BR><BR>
|
||||
<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
|
||||
shown in the left hand navigation sidebar.<BR><BR>
|
||||
<LI><B>Apache license.</B><BR><BR></LI></UL><BR><B>
|
||||
|
|
Loading…
Reference in New Issue