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

Minor doc xref link corrections.

Browse Source
This commit is contained in:
Luke Taylor 2010-06-26 13:14:15 +01:00
parent 71e1702224
commit b6cbdde0cb
7 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -292,7 +292,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 logins).

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

@ -97,7 +97,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 xml:id="core-services-erasing-credentials">
<title>Erasing Credentials on Successful Authentication</title>

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

@ -518,7 +518,7 @@ List&lt;OpenIDAttribute> attributes = token.getAttributes();</programlisting>The
<classname>OpenIDAttribute</classname> contains the attribute type and 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>
Security components in the <link xlink:href="#core-components">technical overview</link>
chapter.</para>
</section>
</section>
@ -624,7 +624,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 annotations</link>. You can
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 pointcuts. </para>

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

@ -166,7 +166,7 @@ class="org.springframework.security.web.authentication.preauth.PreAuthenticatedA
configuration (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 would leave these out
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 roles.

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

@ -103,7 +103,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
<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

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

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

@ -521,7 +521,7 @@ Successfully authenticated. Security context contains: \
and should be consumed by Spring Security's <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>
in the <link xlink:href="#authz-arch">authorization chapter</link>.</para>
</section>
<section>
<title>RunAsManager</title>