Cwikius-Spring/spring-security
1
0
Fork 0
mirror of https://github.com/spring-projects/spring-security.git synced 2025-07-12 21:33:30 +00:00
Code Issues Packages Projects Releases Wiki Activity

Minor corrections to namespace chapter. Fixed image paths for pdf version

Browse Source
This commit is contained in:
Luke Taylor 2008-04-09 23:35:29 +00:00
parent 6de01e0079
commit 10e6ed20cf
5 changed files with 65 additions and 49 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
src/docbkx/authorization-common.xml
View File

@ -95,6 +95,9 @@ public boolean supports(Class clazz);</programlisting></para>
based on voting. Figure 4 illustrates the relevant classes.</para>
<para><mediaobject>
<imageobject role="fo">
<imagedata align="center" fileref="resources/images/AccessDecisionVoting.gif" format="GIF"/>
</imageobject>
<imageobject role="html">
<imagedata align="center" fileref="images/AccessDecisionVoting.gif" format="GIF"/>
</imageobject>
@ -266,7 +269,10 @@ public boolean supports(Class clazz);</programlisting></para>
<para><mediaobject>
<imageobject>
<imagedata align="center" fileref="images/AfterInvocation.gif" format="GIF"/>
<imagedata role="fo" align="center" fileref="resources/images/AfterInvocation.gif" format="GIF"/>
</imageobject>
<imageobject>
<imagedata role="html" align="center" fileref="images/AfterInvocation.gif" format="GIF"/>
</imageobject>
<caption>

9
src/docbkx/domain-acls-old.xml
View File

@ -108,6 +108,9 @@
access control list (ACL) lookups.</para>
<para><mediaobject>
<imageobject>
<imagedata role="fo" align="center" fileref="resources/images/ACLSecurity.gif" format="GIF"/>
</imageobject>
<imageobject role="html">
<imagedata align="center" fileref="images/ACLSecurity.gif" format="GIF"/>
</imageobject>
@ -166,6 +169,9 @@ public AclEntry[] getAcls(java.lang.Object domainInstance, Authentication authen
implementation, which is shown in Figure 7.</para>
<para><mediaobject>
<imageobject role="fo">
<imagedata align="center" fileref="resources/images/BasicAclProvider.gif" format="GIF"/>
</imageobject>
<imageobject role="html">
<imagedata align="center" fileref="images/BasicAclProvider.gif" format="GIF"/>
</imageobject>
@ -457,6 +463,9 @@ END;
for more information.</para>
<mediaobject>
<imageobject role="fo">
<imagedata align="center" fileref="resources/images/Permissions.gif" format="GIF"/>
</imageobject>
<imageobject role="html">
<imagedata align="center" fileref="images/Permissions.gif" format="GIF"/>
</imageobject>

23
src/docbkx/namespace-config.xml
View File

@ -23,7 +23,7 @@
<security:ldap-server />
]]></programlisting>
This is much simpler than wiring up the equivalent Apache Directory Server beans. The most
common alterative configuration requirements are supported by attributes on the
common alternative configuration requirements are supported by attributes on the
<literal>ldap-server</literal>
element and the user is isolated from worrying about which beans they need to be set on and
what the bean property names are.
@ -126,7 +126,7 @@
<section>
<info><title><literal>web.xml</literal> Configuration</title></info>
<para>
The first thing you need to do is add the following fiter declaration to your
The first thing you need to do is add the following filter declaration to your
<literal>web.xml</literal>
file:
<programlisting>
@ -196,7 +196,7 @@
</para>
<para>
At this point you should be able to start up your application and you will be required to
log in to proceed. Try it out, or try experimenting with the "tutorial" sample applicaition
log in to proceed. Try it out, or try experimenting with the "tutorial" sample application
that comes with the project. The above configuration actually adds quite a few services to
the application because we have used the
<literal>auto-config</literal>
@ -222,19 +222,23 @@
</http>
]]>
</programlisting>
These other elements are responsible for setting up form-login, see
These other elements are responsible for setting up form-login,
<link xlink:href="#anonymous">anonymous authentication</link>, basic authentication, logout handling and remember-me services
respectively. They each have attributes which can be used to alter their behaviour. For example, if you
want to supply your own login page, you could use:
<programlisting><![CDATA[
<http auto-config='true'>
<intercept-url pattern="/login.jsp*" filters="none"/>
<intercept-url pattern="/**" access="ROLE_USER" />
<form-login login-page='/login.jsp'/>
</http>
]]>
</programlisting>
Note that you can still use <literal>auto-config</literal>. The <literal>form-login</literal> element just overrides the
default settings. If you want to use basic authentication instead of form login, then change the configuration to
default settings. Also note that we've added an extra <literal>intercept-url</literal> element to say that any requests
for the login page should be excluded from processing by the security filters. Otherwise the request would be matched by
the pattern <literal>/**</literal> and it wouldn't be possible to access the login page itself!
If you want to use basic authentication instead of form login, then change the configuration to
<programlisting><![CDATA[
<http auto-config='true'>
<intercept-url pattern="/**" access="ROLE_USER" />
@ -247,6 +251,7 @@
through a login form embedded in another web page.
</para>
</section>
</section>
<section>
<title>Configuring other Authentication Providers</title>
<para>
@ -273,8 +278,8 @@
</para>
<section><title>Adding a Password Encoder</title>
<para>
Often your password data will be encoded using a hashing algorithm. This is supported by the <literal>&gt;password-encoder&lt;</literal>
element. With SHA-encoded passwords, the original authentication provider configuration would look like this:
Often your password data will be encoded using a hashing algorithm. This is supported by the <literal>&lt;password-encoder&gt;</literal>
element. With SHA encoded passwords, the original authentication provider configuration would look like this:
<programlisting><![CDATA[
<authentication-provider>
<password-encoder hash="sha"/>
@ -295,13 +300,11 @@
<salt-source user-property="username"/>
</password-encoder>
]]></programlisting>
You can use a custom password ecoder bean by using the <literal>ref</literal> attribute of <literal>password-encoder</literal>. This should
You can use a custom password encoder bean by using the <literal>ref</literal> attribute of <literal>password-encoder</literal>. This should
contain the name of a bean in the application context which is an instance of Spring Security's <interfacename>PasswordEncoder</interfacename>
interface.
</para>
</section>
</section>
</section>
</section>
</chapter>

8
src/docbkx/springsecurity.xml
View File

@ -84,16 +84,18 @@
<part xml:id="getting-started">
<title>Getting Started</title>
<partintro>
<para>The remaining parts of this guide provide an in-depth discussion of the
<para>The later parts of this guide provide an in-depth discussion of the
framework architecture and implementation classes, an understanding of which is important
if you need to do any serious customization. In this part, we take a slightly
gentler look at how to get started using some of the features of Spring Security 2.0.
The use of namespace configuration provides a much simpler path to securing
In particular, the use of namespace configuration provides a much simpler path to securing
your application with little or no knowledge of the classes involved, unlike the traditional
Spring bean approach which required you to configure large numbers of beans.
</para>
</partintro>
<xi:include href="introduction.xml" />
<xi:include href="namespace-config.xml" />
</part>
@ -110,8 +112,6 @@
integration.</para>
</partintro>
<xi:include href="introduction.xml" />
<xi:include href="technical-overview.xml" />
<xi:include href="supporting-infrastructure.xml" />

12
src/docbkx/technical-overview.xml
View File

@ -1,8 +1,8 @@
<chapter xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="technical-overview"><info><title>Technical Overview</title></info>
<section xml:id="runtime-environment"><info><title>Runtime Environment</title></info>
<chapter xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="technical-overview">
<info><title>Technical Overview</title></info>
<section xml:id="runtime-environment">
<info><title>Runtime Environment</title></info>
<para>Spring Security is written to execute within a standard Java 1.4
Runtime Environment. It also supports Java 5.0, although the Java
@ -477,11 +477,9 @@ String username = obj.toString();
<imageobject role="html">
<imagedata align="center" fileref="images/SecurityInterception.gif" format="GIF"/>
</imageobject>
<imageobject role="fo">
<imagedata align="center" fileref="images/SecurityInterception.gif" format="GIF"/>
<imagedata align="center" fileref="resources/images/SecurityInterception.gif" format="GIF"/>
</imageobject>
<caption>
<para>Figure 1: The key "secure object" model</para>
</caption>