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

SEC-1340: Minor doc corrections

This commit is contained in:
Luke Taylor 2009-12-22 13:25:10 +00:00
parent e64866ae6a
commit be56d72912
3 changed files with 11 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -9,8 +9,8 @@
supports CAS, and provides an easy migration path from single-application deployments of
Spring Security through to multiple-application deployments secured by an enterprise-wide CAS
server.</para>
<para>You can learn more about CAS at <literal>http://www.ja-sig.org/products/cas/</literal>.
You will also need to visit this site to download the CAS Server files.</para>
<para>You can learn more about CAS at <literal>http://www.ja-sig.org/cas</literal>. You will
also need to visit this site to download the CAS Server files.</para>
</section>
<section xml:id="cas-how-it-works">
<info>
@ -269,8 +269,8 @@
parameter does is tell the CAS login service that a single sign on login is unacceptable.
Instead, the user will need to re-enter their username and password in order to gain access to
the service.</para>
<para>The following beans should be configured to commence the CAS authentication
process (assuming you're using a namespace configuration):</para>
<para>The following beans should be configured to commence the CAS authentication process
(assuming you're using a namespace configuration):</para>
<para>
<programlisting><![CDATA[
<security:authentication-manager alias="authenticationManager">
@ -304,8 +304,8 @@
<para>The <literal>CasAuthenticationFilter</literal> has very similar properties to the
<literal>UsernamePasswordAuthenticationFilter</literal> (used for form-based logins). Each
property is self-explanatory. Note that we've also used the namespace syntax for setting up an
alias to the authentication mnager, since the <literal>CasAuthenticationFilter</literal> needs
a reference to it.</para>
alias to the authentication manager, since the <literal>CasAuthenticationFilter</literal>
needs a reference to it.</para>
<para>For CAS to operate, the <classname>ExceptionTranslationFilter</classname> must have its
<literal>authenticationEntryPoint</literal> property set to the
<literal>CasAuthenticationEntryPoint</literal> bean.</para>

2
docs/manual/src/docbook/channel-security.xml
View File

@ -37,7 +37,7 @@
namespace</link> by means of the <literal>requires-channel</literal> attribute on
the <literal>&lt;intercept-url&gt;</literal> element and this is the simplest (and
recommended approach).</para>
<para>To confiure channel security explicitly, you would define the following the filter in
<para>To configure channel security explicitly, you would define the following the filter in
your application context: <programlisting><![CDATA[
<bean id="channelProcessingFilter"
class="org.springframework.security.web.access.channel.ChannelProcessingFilter">

10
docs/manual/src/docbook/community.xml
View File

@ -17,8 +17,8 @@
enhancement requests if you include corresponding unit tests. This is necessary to
ensure project test coverage is adequately maintained.</para>
<para>You can access the issue tracker at <link
xlink:href="http://jira.springframework.org/browse/SEC"
>http://jira.springframework.org/browse/SEC</link>. </para>
xlink:href="http://jira.springsource.org/browse/SEC"
>http://jira.springsource.org/browse/SEC</link>. </para>
</section>
<section xml:id="becoming-involved">
<info>
@ -41,10 +41,8 @@
<title>Further Information</title>
</info>
<para>Questions and comments on Spring Security are welcome. You can use the Spring
Community Forum web site at <uri xlink:href="http://forum.springframework.org"
Community Forum web site at <uri xlink:href="http://forum.springsource.org"
>http://forum.springsource.org</uri> to discuss Spring Security with other users of
the framework. Remember to use JIRA for bug reports, as explained above. Everyone is
also welcome to join the Acegisecurity-developer mailing list and participate in design
discussions. The traffic volume is very light.</para>
the framework. Remember to use JIRA for bug reports, as explained above.</para>
</section>
</chapter>