SEC-562: More changes of Acegi name in comments, docs etc.
This commit is contained in:
Luke Taylor
@@ -111,7 +111,7 @@
|
||||
<xsl:param name="gentext-key" select="''" />
|
||||
<xsl:variable name="Version">
|
||||
<xsl:if test="//releaseinfo">
|
||||
<xsl:text>Acegi Security </xsl:text><xsl:value-of select="//releaseinfo" /><xsl:text></xsl:text>
|
||||
<xsl:text>Spring Security </xsl:text><xsl:value-of select="//releaseinfo" /><xsl:text></xsl:text>
|
||||
</xsl:if>
|
||||
</xsl:variable>
|
||||
<xsl:choose>
|
||||
|
||||
+253
-249
File diff suppressed because it is too large
Load Diff
+24
-24
@@ -1,12 +1,12 @@
|
||||
--------------------------------
|
||||
Acegi Security System for Spring
|
||||
Spring Security
|
||||
--------------------------------
|
||||
|
||||
What is Acegi Security?
|
||||
What is Spring Security?
|
||||
|
||||
Acegi Security is a powerful, flexible security solution for enterprise software,
|
||||
Spring Security is a powerful, flexible security solution for enterprise software,
|
||||
with a particular emphasis on applications that use
|
||||
{{{http://www.springframework.org/}Spring}}. Using Acegi Security provides your
|
||||
{{{http://www.springframework.org/}Spring}}. Using Spring Security provides your
|
||||
applications with comprehensive authentication, authorization, instance-based access control,
|
||||
channel security and human user detection capabilities.
|
||||
|
||||
@@ -30,12 +30,12 @@ Key Features
|
||||
|
||||
* <<Enterprise-wide single sign on:>> Using JA-SIG's open
|
||||
source {{{http://www.ja-sig.org/products/cas/}Central Authentication Service}} (CAS),
|
||||
the Acegi Security can participate
|
||||
the Spring Security can participate
|
||||
in an enterprise-wide single sign on environment. You no longer need
|
||||
every web application to have its own authentication database. Nor are
|
||||
you restricted to single sign on across a single web container. Advanced
|
||||
single sign on features like proxy support and forced refresh of logins
|
||||
are supported by both CAS and Acegi Security.
|
||||
are supported by both CAS and Spring Security.
|
||||
|
||||
* <<Reuses your Spring expertise:>> We use Spring application
|
||||
contexts for all configuration, which should help Spring developers get
|
||||
@@ -66,7 +66,7 @@ Key Features
|
||||
flexibility without adding security code to your Spring business
|
||||
objects.
|
||||
|
||||
* <<After invocation security:>> Acegi Security can not only protect
|
||||
* <<After invocation security:>> Spring Security can not only protect
|
||||
methods from being invoked in the first place, but it can also
|
||||
deal with the objects returned from the methods. Included implementations
|
||||
of after invocation security can throw an exception or mutate the returned
|
||||
@@ -79,41 +79,41 @@ Key Features
|
||||
or Apache Ant paths, along with pluggable authentication, authorization
|
||||
and run-as replacement managers.
|
||||
|
||||
* <<Channel security:>> Acegi Security can
|
||||
* <<Channel security:>> Spring Security can
|
||||
automatically redirect requests across an appropriate transport channel.
|
||||
Whilst flexible enough to support any of your "channel" requirements (eg
|
||||
the remote user is a human, not a robot), a common channel security
|
||||
feature is to ensure your secure pages will only be available over
|
||||
HTTPS, and your public pages only over HTTP. Acegi Security also
|
||||
HTTPS, and your public pages only over HTTP. Spring Security also
|
||||
supports unusual port combinations (including if accessed via an
|
||||
intermediate server like Apache) and pluggable transport decision
|
||||
managers.
|
||||
|
||||
* <<Supports HTTP BASIC authentication:>> Perfect for remoting
|
||||
protocols or those web applications that prefer a simple browser pop-up
|
||||
(rather than a form login), Acegi Security can directly process HTTP
|
||||
(rather than a form login), Spring Security can directly process HTTP
|
||||
BASIC authentication requests as per RFC 1945.
|
||||
|
||||
* <<Supports HTTP Digest authentication:>> For greater security than
|
||||
offered by BASIC authentcation, Acegi Security also supports Digest Authentication
|
||||
offered by BASIC authentcation, Spring Security also supports Digest Authentication
|
||||
(which never sends the user's password across the wire). Digest Authentication
|
||||
is widely supported by modern browsers. Acegi Security's implementation complies
|
||||
is widely supported by modern browsers. Spring Security's implementation complies
|
||||
with both RFC 2617 and RFC 2069.
|
||||
|
||||
* <<Computer Associates Siteminder support:>> Authentication can be
|
||||
delegated through to CA's Siteminder solution, which is common in large
|
||||
corporate environments.
|
||||
|
||||
* <<X509 (Certificate) support:>> Acegi Security can easily read
|
||||
* <<X509 (Certificate) support:>> Spring Security can easily read
|
||||
client-side X509 certificates for authenticating users.
|
||||
|
||||
* <<LDAP Support:>> Do you have an LDAP directory? Acegi Security can
|
||||
* <<LDAP Support:>> Do you have an LDAP directory? Spring Security can
|
||||
happily authenticate against it.
|
||||
|
||||
* <<Tag library support:>> Your JSP files can use our taglib
|
||||
to ensure that protected content like links and messages are only
|
||||
displayed to users holding the appropriate granted authorities. The taglib
|
||||
also fully integrates with Acegi Security's ACL services, and
|
||||
also fully integrates with Spring Security's ACL services, and
|
||||
obtaining extra information about the logged-in principal.
|
||||
|
||||
* <<Configuration via IoC XML, Commons Attributes, or JDK 5 Annotations:>> You
|
||||
@@ -121,7 +121,7 @@ Key Features
|
||||
project supports configuration via Spring application contexts, as well
|
||||
as Jakarta Commons Attributes and Java 5's annotations feature. Some users
|
||||
(such as those building content management systems) pull configuration data
|
||||
from a database, which exemplifies Acegi Security's flexible configuration
|
||||
from a database, which exemplifies Spring Security's flexible configuration
|
||||
metadata system.
|
||||
|
||||
* <<Various authentication backends:>> We include the ability to
|
||||
@@ -134,14 +134,14 @@ Key Features
|
||||
<<<ApplicationEvent>>> services, you can write your own listeners
|
||||
for authentication-related events, along with authorisation-related events.
|
||||
This enables you to implement account lockout and audit log systems, with
|
||||
complete decoupling from Acegi Security code.
|
||||
complete decoupling from Spring Security code.
|
||||
|
||||
* <<Easy integration with existing databases:>> Our implementations
|
||||
have been designed to make it very easy to use your existing
|
||||
authentication schema and data (without modification). Of course,
|
||||
you can also provide your own Data Access Object if you wish.
|
||||
|
||||
* <<Caching:>> Acegi Security integrates with Spring's {{{http://ehcache.sourceforge.net}EHCACHE}} factory.
|
||||
* <<Caching:>> Spring Security integrates with Spring's {{{http://ehcache.sourceforge.net}EHCACHE}} factory.
|
||||
This flexibility means your database (or other authentication
|
||||
repository) is not repeatedly queried for authentication
|
||||
information.
|
||||
@@ -157,7 +157,7 @@ Key Features
|
||||
corrected quickly.
|
||||
|
||||
* <<Remoting support:>> Does your project use a rich client? Not a
|
||||
problem. Acegi Security integrates with standard Spring remoting
|
||||
problem. Spring Security integrates with standard Spring remoting
|
||||
protocols, because it automatically processes the HTTP BASIC
|
||||
authentication headers they present. Add our BASIC authentication filter
|
||||
to your web.xml and you're done. You can also easily use RMI or Digest
|
||||
@@ -166,7 +166,7 @@ Key Features
|
||||
* <<Advanced password encoding:>> Of course, passwords in your
|
||||
authentication repository need not be in plain text. We support both SHA
|
||||
and MD5 encoding, and also pluggable "salt" providers to maximise
|
||||
password security. Acegi Security doesn't even need to see the password
|
||||
password security. Spring Security doesn't even need to see the password
|
||||
if your backend can use a bind-based strategy for authentication (such as
|
||||
an LDAP directory, or a database login).
|
||||
|
||||
@@ -176,12 +176,12 @@ Key Features
|
||||
object tiers with different security configurations than your backend
|
||||
objects.
|
||||
|
||||
* <<Transparent security propagation:>> Acegi Security can automatically
|
||||
* <<Transparent security propagation:>> Spring Security can automatically
|
||||
transfer its core authentication information from one machine to another,
|
||||
using a variety of protocols including RMI and Spring's HttpInvoker.
|
||||
|
||||
* <<Compatible with HttpServletRequest's security methods:>> Even though
|
||||
Acegi Security can deliver authentication using a range of pluggable mechanisms
|
||||
Spring Security can deliver authentication using a range of pluggable mechanisms
|
||||
(most of which require no web container configuration), we allow you to access
|
||||
the resulting Authentication object via the getRemoteUser() and other
|
||||
security methods on HttpServletRequest.
|
||||
@@ -202,8 +202,8 @@ Key Features
|
||||
using an open source security package leverages the continuous design
|
||||
and code quality improvements that emerge from peer review.
|
||||
|
||||
* <<Community:>> Well-known for its supportive community, Acegi Security
|
||||
* <<Community:>> Well-known for its supportive community, Spring Security
|
||||
has an active group of developers and users. Visit our project resources (below)
|
||||
to access these services.
|
||||
|
||||
* <<Apache license.>> You can confidently use Acegi Security in your project.
|
||||
* <<Apache license.>> You can confidently use Spring Security in your project.
|
||||
|
||||
@@ -10,10 +10,10 @@ Tutorial: Adding Security to Spring Petclinic
|
||||
* Preparation
|
||||
|
||||
To complete this tutorial, you will require a servlet container (such as Tomcat)
|
||||
and a general understanding of using Spring without Acegi Security. The Petclinic
|
||||
and a general understanding of using Spring without Spring Security. The Petclinic
|
||||
sample itself is part of Spring and should help you learn Spring. We suggest you
|
||||
only try to learn one thing at a time, and start with Spring/Petclinic before
|
||||
Acegi Security.
|
||||
Spring Security.
|
||||
|
||||
|
||||
|
||||
@@ -21,18 +21,18 @@ Tutorial: Adding Security to Spring Petclinic
|
||||
|
||||
* Spring 2.0 M4 with dependencies ZIP file
|
||||
|
||||
* Acegi Security 1.0.2
|
||||
* Spring Security 1.0.2
|
||||
|
||||
|
||||
Unzip both files. After unzipping Acegi Security, you'll need to unzip the
|
||||
acegi-security-sample-tutorial.war file, because we need some files that are
|
||||
Unzip both files. After unzipping Spring Security, you'll need to unzip the
|
||||
spring-security-sample-tutorial.war file, because we need some files that are
|
||||
included within it. In the code below, we'll refer to the respective unzipped
|
||||
locations as %spring% and %acegi% (with the latter variable referring to the
|
||||
unzipped WAR, not the original ZIP). There is no need to setup any environment
|
||||
variables to complete the tutorial.
|
||||
|
||||
|
||||
* Add required Acegi Security files to Petclinic
|
||||
* Add required Spring Security files to Petclinic
|
||||
|
||||
|
||||
We now need to put some extra files into Petclinic. The following commands should work:
|
||||
@@ -56,7 +56,7 @@ copy %acegi%\WEB-INF\lib\commons-codec-1.3.jar %spring%\samples\petclinic\war\WE
|
||||
+------------------------------------------------------
|
||||
|
||||
<filter>
|
||||
<filter-name>Acegi Filter Chain Proxy</filter-name>
|
||||
<filter-name>Spring Security Filter Chain Proxy</filter-name>
|
||||
<filter-class>org.springframework.security.util.FilterToBeanProxy</filter-class>
|
||||
<init-param>
|
||||
<param-name>targetClass</param-name>
|
||||
@@ -65,7 +65,7 @@ copy %acegi%\WEB-INF\lib\commons-codec-1.3.jar %spring%\samples\petclinic\war\WE
|
||||
</filter>
|
||||
|
||||
<filter-mapping>
|
||||
<filter-name>Acegi Filter Chain Proxy</filter-name>
|
||||
<filter-name>Spring Security Filter Chain Proxy</filter-name>
|
||||
<url-pattern>/*</url-pattern>
|
||||
</filter-mapping>
|
||||
|
||||
@@ -194,7 +194,7 @@ copy dist\petclinic.war %TOMCAT_HOME%\webapps
|
||||
You will receive an access denied error when you attempt to add a visit.
|
||||
|
||||
To clean things up a bit, you might want to wrap up by hiding the "add visit" link
|
||||
unless you are authorized to use it. Acegi Security provides a tag library to help
|
||||
unless you are authorized to use it. Spring Security provides a tag library to help
|
||||
you do that. Edit %spring%\samples\petclinic\war\WEB-INF\jsp\owner.jsp. Add
|
||||
the following line to the top of the file:
|
||||
|
||||
@@ -220,6 +220,6 @@ copy dist\petclinic.war %TOMCAT_HOME%\webapps
|
||||
These steps can be applied to your own application. Although we do suggest
|
||||
that you visit <a href="http://acegisecurity.org">http://acegisecurity.org</a>
|
||||
and in particular review the "Suggested Steps" for getting started with Acegi
|
||||
Security. The suggested steps are optimized for learning Acegi Security quickly
|
||||
Security. The suggested steps are optimized for learning Spring Security quickly
|
||||
and applying it to your own projects. It also includes realistic time estimates
|
||||
for each step so you can plan your integration activities.</p>
|
||||
|
||||
+10
-10
@@ -1,11 +1,11 @@
|
||||
--------------------------------
|
||||
Acegi Security Suggested Steps
|
||||
Spring Security Suggested Steps
|
||||
--------------------------------
|
||||
|
||||
Suggested Steps
|
||||
|
||||
Presented below are the steps we encourage you to take in order to gain the most
|
||||
out of Acegi Security in a realistic timeframe.
|
||||
out of Spring Security in a realistic timeframe.
|
||||
|
||||
|
||||
[[1]] First of all, deploy the "Tutorial Sample", which is included in the main distribution
|
||||
@@ -16,9 +16,9 @@ Suggested Steps
|
||||
|
||||
|
||||
[[2]] Next, follow the {{{petclinic-tutorial.html}Petclinic Tutorial}}, which
|
||||
covers how to add Acegi Security to the commonly-used Petclinic sample application
|
||||
covers how to add Spring Security to the commonly-used Petclinic sample application
|
||||
that ships with Spring. This will give you a hands-on approach to integrating
|
||||
Acegi Security into your own application.
|
||||
Spring Security into your own application.
|
||||
|
||||
Estimated time: 1 hour.
|
||||
|
||||
@@ -32,10 +32,10 @@ Suggested Steps
|
||||
Estimated time: 1 day.
|
||||
|
||||
[[4]] If you have relatively simple security needs, you can probably start to integrate
|
||||
Acegi Security into your application at this point. Just use the "Tutorial Sample"
|
||||
Spring Security into your application at this point. Just use the "Tutorial Sample"
|
||||
as your basis (now that you understand how it works). Those with more complicated
|
||||
requirements should review the "Contacts Sample" application.
|
||||
This will probably involve deploying <<<acegi-security-sample-contacts-filter.war>>>,
|
||||
This will probably involve deploying <<<spring-security-sample-contacts-filter.war>>>,
|
||||
which is also included in the release ZIP file.
|
||||
|
||||
The purpose of understanding the "Contacts Sample" is to get a better feel for how method
|
||||
@@ -66,7 +66,7 @@ Suggested Steps
|
||||
Estimated time: 1-2 days.
|
||||
|
||||
|
||||
[[5]]By now you will have a good grasp on how Acegi Security works, and all that is left to
|
||||
[[5]]By now you will have a good grasp on how Spring Security works, and all that is left to
|
||||
do is design your own application's implementation.
|
||||
|
||||
|
||||
@@ -81,7 +81,7 @@ Suggested Steps
|
||||
{{{reference.html}Reference Guide}},
|
||||
{{{http://www.springframework.org}forums}}, and
|
||||
{{{faq.html}FAQ}}
|
||||
for help, you'll find it pretty easy to implement Acegi Security in your application.
|
||||
for help, you'll find it pretty easy to implement Spring Security in your application.
|
||||
Most importantly, you'll be using a security framework that offers you complete container
|
||||
portability, flexibility, and community support - without needing to write and maintain your
|
||||
own code.
|
||||
@@ -93,10 +93,10 @@ Suggested Steps
|
||||
on how much experience you have, particularly with Java and Spring. They will also vary depending
|
||||
on how complex your intended security-enabled application will be. Some people need to push the domain
|
||||
object instance access control list capabilities to the maximum, whilst others don't even need anything
|
||||
beyond web request security. The good thing is Acegi Security will either directly support your future
|
||||
beyond web request security. The good thing is Spring Security will either directly support your future
|
||||
needs, or provide a clearly-defined extension point for addressing them.
|
||||
|
||||
|
||||
We welcome your feedback about how long it has actually taken you to complete each step, so we
|
||||
can update this page and help new users better assess their project timetables in the future.
|
||||
Any other tips on what you found helpful in learning Acegi Security are also very welcome.
|
||||
Any other tips on what you found helpful in learning Spring Security are also very welcome.
|
||||
|
||||
@@ -2,9 +2,9 @@
|
||||
|
||||
--- Sample Hypersonic SQL compatible schema and data
|
||||
---
|
||||
--- All Acegi Security JDBC DAOs can be customised to use a different schema.
|
||||
--- In addition, the Acegi Security JDBC DAOs do not even need to be used
|
||||
--- with Acegi Security, and an entirely customised persistence strategy
|
||||
--- All Spring Security JDBC DAOs can be customised to use a different schema.
|
||||
--- In addition, the Spring Security JDBC DAOs do not even need to be used
|
||||
--- with Spring Security, and an entirely customised persistence strategy
|
||||
--- can be employed via standard interfaces (eg in-memory, Hibernate etc).
|
||||
|
||||
SET IGNORECASE TRUE;
|
||||
|
||||
+5
-5
@@ -20,21 +20,21 @@
|
||||
* ========================================================================
|
||||
-->
|
||||
|
||||
<project name="Acegi Security">
|
||||
<project name="Spring Security">
|
||||
<bannerLeft>
|
||||
<name>Acegi Security on Sourceforge</name>
|
||||
<name>Spring Security on Sourceforge</name>
|
||||
<src>http://sourceforge.net/sflogo.php?group_id=104215&type=5</src>
|
||||
<href>http://sourceforge.net/projects/acegisecurity</href>
|
||||
</bannerLeft>
|
||||
<bannerRight>
|
||||
<name>Acegi Security</name>
|
||||
<name>Spring Security</name>
|
||||
<src>images/logo.gif</src>
|
||||
<href>http://acegisecurity.org/</href>
|
||||
</bannerRight>
|
||||
|
||||
<body>
|
||||
<links>
|
||||
<item name="Acegi Security on Sourceforge" href="http://sourceforge.net/projects/acegisecurity" />
|
||||
<item name="Spring Security on Sourceforge" href="http://sourceforge.net/projects/acegisecurity" />
|
||||
</links>
|
||||
|
||||
<menu name="Overview">
|
||||
@@ -58,7 +58,7 @@
|
||||
<item name="Core JavaDocs" href="spring-security-core/apidocs/index.html" target="_blank"/>
|
||||
<item name="Contacts HTTPS" href="spring-security-samples/spring-security-samples-contacts/sslhowto.txt"/>
|
||||
<item name="Project Policies" href="policies.html"/>
|
||||
<item name="Acegi Security JIRA" href="http://opensource.atlassian.com/projects/spring/secure/BrowseProject.jspa?id=10040"/>
|
||||
<item name="Spring Security JIRA" href="http://opensource.atlassian.com/projects/spring/secure/BrowseProject.jspa?id=10040"/>
|
||||
<item name="Support Forum" href="http://forum.springframework.org/forumdisplay.php?f=33"/>
|
||||
<item name="Core Reports" href="spring-security-core/project-reports.html"/>
|
||||
</menu>
|
||||
|
||||
@@ -1,14 +1,14 @@
|
||||
<?xml version="1.0" encoding="ISO-8859-1"?>
|
||||
<document><properties><title>External Web Articles covering Acegi Security</title></properties><body><section name="External Web Articles covering Acegi Security"><p>Here are some of the external pages mentioning Acegi Security. If you've
|
||||
<document><properties><title>External Web Articles covering Spring Security</title></properties><body><section name="External Web Articles covering Spring Security"><p>Here are some of the external pages mentioning Spring Security. If you've
|
||||
found another, please let us know.
|
||||
<ul>
|
||||
<li><b><a href="http://forum.springframework.org">Spring Forums</a></b>:
|
||||
The first place to look for Acegi Security support (use the 'search' function).<br></br><br></br>
|
||||
The first place to look for Spring Security support (use the 'search' function).<br></br><br></br>
|
||||
</li>
|
||||
<li><b><a href="mail-lists.html">Acegi Security Mailing Lists</a></b>:
|
||||
<li><b><a href="mail-lists.html">Spring Security Mailing Lists</a></b>:
|
||||
If you'd like to discuss development of the project.<br></br><br></br>
|
||||
</li>
|
||||
<li><b><a href="powering.html">Numerous frameworks using Acegi Security</a></b>:
|
||||
<li><b><a href="powering.html">Numerous frameworks using Spring Security</a></b>:
|
||||
Look here first for how to integrate with major third-party frameworks...<br></br><br></br>
|
||||
</li>
|
||||
<li><b><a href="http://www.vorburger.ch/blog1/2006/10/propagating-acegis-security-context-in.html">Propagating Acegi Security's Context in a WSS UsernameToken SOAP Header via XFire using WSS4J</a></b>:
|
||||
@@ -141,7 +141,7 @@
|
||||
</li>
|
||||
<li><b><a href="http://jakarta.apache.org/commons/attributes/faq.html">Anyone else using C-A (Commons Attributes)?</a></b>: Acegi Security made the list
|
||||
of projects using Jakarta Commons Attributes. Our
|
||||
<a href="/multiproject/acegi-security-sample-attributes/index.html">Attributes Sample</a>
|
||||
<a href="/multiproject/spring-security-sample-attributes/index.html">Attributes Sample</a>
|
||||
demonstrates C-A integration.<br></br><br></br>
|
||||
</li>
|
||||
<li><b><a href="http://www.arroco.com/cgi-bin/blosxom.cgi/2005/08/22#acegi-javadoc">Documenting the Future At the Expense of the Present</a></b>:
|
||||
|
||||
@@ -2,18 +2,18 @@
|
||||
<document>
|
||||
<properties><title>Building</title></properties>
|
||||
<body>
|
||||
<section name="Building Acegi Security System">
|
||||
<section name="Building Spring Security">
|
||||
|
||||
<subsection name="Checking Out from Subversion (SVN)">
|
||||
|
||||
<p>This project uses <a href="http://maven.apache.org/">Maven</a> as project manager
|
||||
and build tool. We recommend you to install Maven 2.0.5 or greater before trying
|
||||
the following.</p><p>To checkout Acegi Security from SVN, see our
|
||||
the following.</p><p>To checkout Spring Security from SVN, see our
|
||||
<a href="svn-usage.html">SVN Usage</a> page.</p>
|
||||
|
||||
</subsection>
|
||||
|
||||
<subsection name="Quick Build"><p>Often people reading this document just want to see if Acegi Security will work
|
||||
<subsection name="Quick Build"><p>Often people reading this document just want to see if Spring Security will work
|
||||
for their projects. They want to deploy a sample application, and that's about it
|
||||
(after all, all the reference documentation can be read online at
|
||||
<a href="http://acegisecurity.org/">http://acegisecurity.org</a>).
|
||||
|
||||
@@ -27,7 +27,7 @@
|
||||
|
||||
<document>
|
||||
<properties>
|
||||
<title>Acegi Security changes</title>
|
||||
<title>Spring Security changes</title>
|
||||
</properties>
|
||||
<body>
|
||||
<release version="1.0.0 Final" date="In CVS">
|
||||
|
||||
@@ -1,14 +1,14 @@
|
||||
<?xml version="1.0" encoding="ISO-8859-1"?>
|
||||
<document>
|
||||
<properties>
|
||||
<title>Acegi Security Downloads</title>
|
||||
<title>Spring Security Downloads</title>
|
||||
</properties>
|
||||
<body>
|
||||
<section name="Acegi Security Downloads">
|
||||
<section name="Spring Security Downloads">
|
||||
<p>
|
||||
If you wish to try out this project, you are probably
|
||||
looking for the
|
||||
<strong>acegi-security-xx.zip</strong>
|
||||
<strong>spring-security-xx.zip</strong>
|
||||
file, which contains all of the officially released
|
||||
JARs, a copy of all documentation, and two WAR
|
||||
artifacts. The two WAR artifacts are from the Contacts
|
||||
@@ -19,9 +19,9 @@
|
||||
</p>
|
||||
|
||||
<p>
|
||||
The acegi-security-xx-src.zip is intended for use with
|
||||
The spring-security-xx-src.zip is intended for use with
|
||||
IDEs. It does not contain the files needed to compile
|
||||
Acegi Security. It also does not contain the sources to
|
||||
Spring Security. It also does not contain the sources to
|
||||
the sample applications. If you need any of these files,
|
||||
please download from SVN.
|
||||
</p>
|
||||
@@ -38,7 +38,7 @@
|
||||
</subsection>
|
||||
<subsection name="Maven Dependencies">
|
||||
<p>
|
||||
The Acegi Security JARs are also available via the
|
||||
The Spring Security JARs are also available via the
|
||||
<a
|
||||
href="http://repo1.maven.org/maven2/org/acegisecurity">
|
||||
Central Maven Repository
|
||||
|
||||
@@ -117,7 +117,7 @@
|
||||
|
||||
<subsection name="Is it called "Acegi" or "Acegi Security"?">
|
||||
|
||||
<p>It's official name is <i>Acegi Security System for Spring</i>,
|
||||
<p>It's official name is <i>Spring Security</i>,
|
||||
although we're happy for it to be abbreviated to
|
||||
<i>Acegi Security</i>. Please don't just call it <i>Acegi</i>, though,
|
||||
as that gets confused with the name of the company that maintains Acegi
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
<?xml version="1.0" encoding="ISO-8859-1"?>
|
||||
<document><properties><title>Project Policies and Procedures</title></properties><body><section name="Project Policies and Procedures Version 1.0"><p>The following policies and procedures are intended to ensure that Acegi Security will
|
||||
<document><properties><title>Project Policies and Procedures</title></properties><body><section name="Project Policies and Procedures Version 1.0"><p>The following policies and procedures are intended to ensure that Spring Security will
|
||||
continue to achieve its project objectives and support the community in the context of an
|
||||
expanding development team.
|
||||
|
||||
@@ -55,7 +55,7 @@
|
||||
</li>
|
||||
|
||||
<li>
|
||||
Developers please keep an eye on the <a href="http://forum.springframework.org">Acegi Security forum</a>. It's a very active forum, and it takes a lot of work if not shared around. Please don't hesitate to reply to users - I try to read every thread and correct/confirm the situation if someone mentions they're unsure. I also will generally send developers an email if there's a question I can't answer as I didn't write the code.<br></br><br></br>
|
||||
Developers please keep an eye on the <a href="http://forum.springframework.org">Spring Security forum</a>. It's a very active forum, and it takes a lot of work if not shared around. Please don't hesitate to reply to users - I try to read every thread and correct/confirm the situation if someone mentions they're unsure. I also will generally send developers an email if there's a question I can't answer as I didn't write the code.<br></br><br></br>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
|
||||
@@ -1,10 +1,10 @@
|
||||
<?xml version="1.0" encoding="ISO-8859-1"?>
|
||||
<document><properties><title>Products Using Acegi Security</title></properties><body><section name="Products Using Acegi Security"><p>Many open source and commercial products either use Acegi Security or at least
|
||||
<document><properties><title>Products Using Spring Security</title></properties><body><section name="Products Using Acegi Security"><p>Many open source and commercial products either use Acegi Security or at least
|
||||
support it. Following is a partial list of such products. If you've integrated Acegi
|
||||
Security with some other product, please let us know (preferably with a URL
|
||||
to some page explaining the integration/use)...
|
||||
|
||||
</p><subsection name="Out-Of-the-Box Supported by Acegi Security"><ul>
|
||||
</p><subsection name="Out-Of-the-Box Supported by Spring Security"><ul>
|
||||
<li><b><a href="http://springframework.org/">Spring Framework</a></b>: J2EE abstraction framework.<br></br><br></br></li>
|
||||
<li><b><a href="http://eclipse.org/aspectj/">AspectJ</a></b>: AOP framework.<br></br><br></br></li>
|
||||
<li><b><a href="http://jcaptcha.sourceforge.net/">JCaptcha</a></b>: Detects human users.<br></br><br></br></li>
|
||||
@@ -30,10 +30,10 @@
|
||||
<li><b><a href="http://plazma.sourceforge.net/">Plazma</a></b>: Swing-based ERP and CRM system for SMEs.<br></br><br></br></li>
|
||||
<li><b><a href="http://www.jasypt.org/">Jasypt</a></b>: Java encryption project. <a href="http://www.jasypt.org/faq.html#i-am-already-using-spring-security-for-encrypting-passwords">Integration details</a>.<br></br><br></br></li>
|
||||
</ul></subsection><subsection name="Commercial Deployments"><ul>
|
||||
<li>A global financial institution uses Acegi Security's SiteMinder integration in a physical security management application.<br></br><br></br></li>
|
||||
<li>A central bank that uses Acegi Security for many of its internal applications with the CAS integration.<br></br><br></br></li>
|
||||
<li>Several Australian Government departments use Acegi Security for securing SOAP-based web services and web applications.<br></br><br></br></li>
|
||||
<li>Enterprise Systems and Services at Rutgers University uses Acegi Security in conjunction with JA-SIG Central Authentication Service to provide authentication and authorization capabilities to its applications including those used by staff and students as well as those utilized by web services.<br></br><br></br></li>
|
||||
<li><a href="http://www.elasticpath.com/ecommerce/architecture/soa.jsp">Elastic Path</a> uses Acegi Security for security.<br></br><br></br></li>
|
||||
<li>A global financial institution uses Spring Security's SiteMinder integration in a physical security management application.<br></br><br></br></li>
|
||||
<li>A central bank that uses Spring Security for many of its internal applications with the CAS integration.<br></br><br></br></li>
|
||||
<li>Several Australian Government departments use Spring Security for securing SOAP-based web services and web applications.<br></br><br></br></li>
|
||||
<li>Enterprise Systems and Services at Rutgers University uses Spring Security in conjunction with JA-SIG Central Authentication Service to provide authentication and authorization capabilities to its applications including those used by staff and students as well as those utilized by web services.<br></br><br></br></li>
|
||||
<li><a href="http://www.elasticpath.com/ecommerce/architecture/soa.jsp">Elastic Path</a> uses Spring Security for security.<br></br><br></br></li>
|
||||
<li>Plus many more... ;-)<br></br><br></br></li>
|
||||
</ul></subsection></section></body></document>
|
||||
@@ -56,7 +56,7 @@ Locate and remove all property references to
|
||||
in web.xml match the following:<br></br><br></br>
|
||||
<code>
|
||||
<filter><br></br>
|
||||
<filter-name>Acegi Security System for Spring Auto Integration Filter</filter-name><br></br>
|
||||
<filter-name>Spring Security Auto Integration Filter</filter-name><br></br>
|
||||
<filter-class>net.sf.acegisecurity.util.FilterToBeanProxy</filter-class><br></br>
|
||||
<init-param><br></br>
|
||||
<param-name>targetClass</param-name><br></br>
|
||||
|
||||
Reference in New Issue
Block a user