From f28a09dfa4623d85e363709bf70b0f6542d6c817 Mon Sep 17 00:00:00 2001 From: Rob Winch Date: Sun, 17 Apr 2011 17:12:59 -0500 Subject: [PATCH] Formatting changes to CAS documentation --- docs/manual/src/docbook/cas-auth-provider.xml | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/docs/manual/src/docbook/cas-auth-provider.xml b/docs/manual/src/docbook/cas-auth-provider.xml index 3665811066..0a610dac02 100644 --- a/docs/manual/src/docbook/cas-auth-provider.xml +++ b/docs/manual/src/docbook/cas-auth-provider.xml @@ -285,7 +285,7 @@ - + @@ -298,7 +298,7 @@ UserDetailsService instance to load the authorities for a user, once they have been authenticated by CAS. We've shown a simple in-memory setup here. Note that the CasAuthenticationProvider does not actually use - the password for authentication. + the password for authentication, but it does use the authorities. The beans are all reasonably self-explanatory if you refer back to the How CAS Works section. This completes the most basic configuration for CAS. If you haven't made any @@ -328,8 +328,8 @@ class="org.springframework.security.web.authentication.logout.LogoutFilter"> - + @@ -456,7 +456,8 @@ // NOTE: The CasAuthenticationToken can also be obtained using // SecurityContextHolder.getContext().getAuthentication() final CasAuthenticationToken token = (CasAuthenticationToken) request.getUserPrincipal(); - // proxyTicket could be reused to make calls to to the CAS service even if the target url differs + // proxyTicket could be reused to make calls to the CAS service even if the + // target url differs final String proxyTicket = token.getAssertion().getPrincipal().getProxyTicketFor(targetUrl); // Make a remote call using the proxy ticket @@ -524,8 +525,8 @@ ... - + ]]>