root
/
spring-security
mirror of https://github.com/spring-projects/spring-security.git
1
0
Fork 0
Code Issues Actions 6 Packages Projects Releases Wiki Activity

Minor doc link updates and tidying.

This commit is contained in:
Luke Taylor 2010-06-26 13:20:48 +01:00
parent ad82e6a575
commit 4da4734750
8 changed files with 18 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
docs/manual/src/docbook/authorization-common.xml
View File

@ -177,14 +177,14 @@ boolean supports(Class clazz);
<title>Custom Voters</title>
<para>Obviously, you can also implement a custom
<interfacename>AccessDecisionVoter</interfacename> and you can
put just about any access-control logic you want in it. It might
be specific to your application (business-logic related) or it
might implement some security administration logic. For example, you'll find
a <link xlink:href='http://blog.springsource.com/2009/01/02/spring-security-customization-part-2-adjusting-secured-session-in-real-time/'>
blog article</link> on the SpringSource web site which describes how to
use a voter to deny access in real-time to users whose accounts have
been suspended.
</para>
put just about any access-control logic you want in it. It might
be specific to your application (business-logic related) or it
might implement some security administration logic. For example, you'll find
a <link xlink:href='http://blog.springsource.com/2009/01/02/spring-security-customization-part-2-adjusting-secured-session-in-real-time/'>
blog article</link> on the SpringSource web site which describes how to
use a voter to deny access in real-time to users whose accounts have
been suspended.
</para>
</section>
</section>
</section>

2
docs/manual/src/docbook/cas-auth-provider.xml
View File

@ -291,7 +291,7 @@
]]>
</programlisting> </para>
<para> The <classname>CasAuthenticationEntryPoint</classname> should be selected to drive
authentication using <link xlink:href="ns-entry-point-ref"
authentication using <link xlink:href="#ns-entry-point-ref"
><literal>entry-point-ref</literal></link>. </para>
<para>The <classname>CasAuthenticationFilter</classname> has very similar properties to the
<classname>UsernamePasswordAuthenticationFilter</classname> (used for form-based

2
docs/manual/src/docbook/core-services.xml
View File

@ -117,7 +117,7 @@
<interfacename>SaltSource</interfacename> enables the passwords to be populated with
a "salt", which enhances the security of the passwords in the authentication
repository. These will be discussed in more detail <link
xlink:href="core-services-password-encodin">below</link>. </para>
xlink:href="#core-services-password-encoding">below</link>. </para>
</section>
</section>
<section>

6
docs/manual/src/docbook/namespace-config.xml
View File

@ -599,7 +599,7 @@ List&lt;OpenIDAttribute> attributes = token.getAttributes();</programlisting>The
retrieved value (or values in the case of multi-valued attributes). We'll see
more about how the <classname>SecurityContextHolder</classname> class is used
when we look at core Spring Security components in the <link
xlink:href="core-components">technical overview</link> chapter. Multiple
xlink:href="#core-components">technical overview</link> chapter. Multiple
attribute exchange configurations are also be supported, if you wish to use
multiple identity providers. You can supply multiple
<literal>attribute-exchange</literal> elements, using an
@ -786,7 +786,7 @@ List&lt;OpenIDAttribute> attributes = token.getAttributes();</programlisting>The
<para>From version 2.0 onwards Spring Security has improved support substantially for adding
security to your service layer methods. It provides support for JSR-250 annotation
security as well as the framework's original <literal>@Secured</literal> annotation.
From 3.0 you can also make use of new <link xlink:href="el-access">expression-based
From 3.0 you can also make use of new <link xlink:href="#el-access">expression-based
annotations</link>. You can apply security to a single bean, using the
<literal>intercept-methods</literal> element to decorate the bean declaration, or
you can secure multiple beans across the entire service layer using the AspectJ style
@ -887,7 +887,7 @@ List&lt;OpenIDAttribute> attributes = token.getAttributes();</programlisting>The
<para> The default strategy is to use an <classname>AffirmativeBased</classname>
<interfacename>AccessDecisionManager</interfacename> with a
<classname>RoleVoter</classname> and an <classname>AuthenticatedVoter</classname>.
You can find out more about these in the chapter on <link xlink:href="authorization"
You can find out more about these in the chapter on <link xlink:href="#authz-arch"
>authorization</link>.</para>
<section xml:id="ns-custom-access-mgr">
<title>Customizing the AccessDecisionManager</title>

2
docs/manual/src/docbook/preauth.xml
View File

@ -178,7 +178,7 @@ class="org.springframework.security.web.authentication.preauth.PreAuthenticatedA
(hence the user of the <literal>custom-filter</literal>,
<literal>authentication-manager</literal> and
<literal>custom-authentication-provider</literal> elements (you can read more
about them in the <link xlink:href="ns-config">namespace chapter</link>). You
about them in the <link xlink:href="#ns-config">namespace chapter</link>). You
would leave these out of a traditional bean configuration. It's also assumed
that you have added a <interfacename>UserDetailsService</interfacename> (called
<quote>userDetailsService</quote>) to your configuration to load the user's

4
docs/manual/src/docbook/samples.xml
View File

@ -17,7 +17,7 @@
<para> The tutorial sample is a nice basic example to get you started. It uses simple
namespace configuration throughout. The compiled application is included in the
distribution zip file, ready to be deployed into your web container
(<filename>spring-security-samples-tutorial-3.0.x.war</filename>). The <link
(<filename>spring-security-samples-tutorial-3.1.x.war</filename>). The <link
xlink:href="#ns-form-and-basic">form-based</link> authentication mechanism is used in
combination with the commonly-used <link xlink:href="#remember-me">remember-me</link>
authentication provider to automatically remember the login using cookies.</para>
@ -123,7 +123,7 @@ Success! Your web filters appear to be properly configured!
<title>CAS Sample</title>
<para> The CAS sample requires that you run both a CAS server and CAS client. It isn't
included in the distribution so you should check out the project code as described in
<link xlink:href="get-source">the introduction</link>. You'll find the relevant files
<link xlink:href="#get-source">the introduction</link>. You'll find the relevant files
under the <filename>sample/cas</filename> directory. There's also a
<filename>Readme.txt</filename> file in there which explains how to run both the server
and the client directly from the source tree, complete with SSL support. You have to

2
docs/manual/src/docbook/taglibs.xml
View File

@ -16,7 +16,7 @@
Spring Security 3.0, it can be used in two ways <footnote>
<para>The legacy options from Spring Security 2.0 are also supported, but
discouraged.</para>
</footnote>. The first approach uses a <link xlink:href="el-access-we">web-security
</footnote>. The first approach uses a <link xlink:href="#el-access-web">web-security
expression</link>, specified in the <literal>access</literal> attribute of the tag. The
expression evaluation will be delegated to the
<interfacename>WebSecurityExpressionHandler</interfacename> defined in the application

2
docs/manual/src/docbook/technical-overview.xml
View File

@ -582,7 +582,7 @@ Successfully authenticated. Security context contains: \
<classname>RoleVoter</classname>. This is only relevant when a voter-based
<interfacename>AccessDecisionManager</interfacename> is in use. We'll see how
the <interfacename>AccessDecisionManager</interfacename> is implemented in the
<link xlink:href="authz-arch">authorization chapter</link>.</para>
<link xlink:href="#authz-arch">authorization chapter</link>.</para>
</section>
<section>
<title>RunAsManager</title>