Removed references to Acegi in contacts sample home page
This commit is contained in:
parent
78065ba47c
commit
f3b3004085
|
@ -4,7 +4,7 @@
|
||||||
<head><title>Contacts Security Demo</title></head>
|
<head><title>Contacts Security Demo</title></head>
|
||||||
<body>
|
<body>
|
||||||
<h1>Contacts Security Demo</h1>
|
<h1>Contacts Security Demo</h1>
|
||||||
<P>Contacts demonstrates the following central Acegi Security capabilities:
|
<P>Contacts demonstrates the following central Spring Security capabilities:
|
||||||
<ul>
|
<ul>
|
||||||
<li><b>Role-based security</b>. Each principal is a member of certain roles,
|
<li><b>Role-based security</b>. Each principal is a member of certain roles,
|
||||||
which are used to restrict access to certain secure objects.</li>
|
which are used to restrict access to certain secure objects.</li>
|
||||||
|
@ -15,20 +15,20 @@
|
||||||
layer bean has a number of secured (protected) and public (unprotected)
|
layer bean has a number of secured (protected) and public (unprotected)
|
||||||
methods.</li>
|
methods.</li>
|
||||||
<li><b>Web request security</b>. The <code>/secure</code> URI path is protected
|
<li><b>Web request security</b>. The <code>/secure</code> URI path is protected
|
||||||
by Acegi Security from principals not holding the
|
by Spring Security from principals not holding the
|
||||||
<code>ROLE_USER</code> granted authority.</li>
|
<code>ROLE_USER</code> granted authority.</li>
|
||||||
<li><b>Security unaware application objects</b>. None of the objects
|
<li><b>Security unaware application objects</b>. None of the objects
|
||||||
are aware of the security being implemented by Acegi Security. *</li>
|
are aware of the security being implemented by Spring Security. *</li>
|
||||||
<li><b>Security taglib usage</b>. All of the JSPs use Acegi Security's
|
<li><b>Security taglib usage</b>. All of the JSPs use Spring Security's
|
||||||
taglib to evaluate security information. *</li>
|
taglib to evaluate security information. *</li>
|
||||||
<li><b>Fully declarative security</b>. Every capability is configured in
|
<li><b>Fully declarative security</b>. Every capability is configured in
|
||||||
the application context using standard Acegi Security classes. *</li>
|
the application context using standard Spring Security classes. *</li>
|
||||||
<li><b>Database-sourced security data</b>. All of the user, role and ACL
|
<li><b>Database-sourced security data</b>. All of the user, role and ACL
|
||||||
information is obtained from an in-memory JDBC-compliant database.</li>
|
information is obtained from an in-memory JDBC-compliant database.</li>
|
||||||
<li><b>Integrated form-based and BASIC authentication</b>. Any BASIC
|
<li><b>Integrated form-based and BASIC authentication</b>. Any BASIC
|
||||||
authentication header is detected and used for authentication. Normal
|
authentication header is detected and used for authentication. Normal
|
||||||
interactive form-based authentication is used by default.</li>
|
interactive form-based authentication is used by default.</li>
|
||||||
<li><b>Remember-me services</b>. Acegi Security's pluggable remember-me
|
<li><b>Remember-me services</b>. Spring Security's pluggable remember-me
|
||||||
strategy is demonstrated, with a corresponding checkbox on the login form.</li>
|
strategy is demonstrated, with a corresponding checkbox on the login form.</li>
|
||||||
</ul>
|
</ul>
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue