SEC-1905: Added para tag to the digest encoded password footnote

This commit is contained in:
Rob Winch 2012-07-11 13:12:57 -05:00
parent bfd09f7603
commit b196d70f99

View File

@ -138,11 +138,11 @@
<para>The configured <interfacename>UserDetailsService</interfacename> is needed because
<literal>DigestAuthenticationFilter</literal> must have direct access to the clear
text password of a user. Digest Authentication will NOT work if you are using
encoded passwords in your DAO <footnote>It is possible to encode the password in the
encoded passwords in your DAO <footnote><para>It is possible to encode the password in the
format HEX( MD5(username:realm:password) ) provided the
<code>DigestAuthenticationFilter.passwordAlreadyEncoded</code> is set to <code>true</code>.
However, other password encodings will not work with digest authentication.</footnote>. The DAO
collaborator, along with the <literal>UserCache</literal>, are typically shared directly
However, other password encodings will not work with digest authentication.</para></footnote>.
The DAO collaborator, along with the <literal>UserCache</literal>, are typically shared directly
with a <classname>DaoAuthenticationProvider</classname>. The
<literal>authenticationEntryPoint</literal> property must be
<classname>DigestAuthenticationEntryPoint</classname>, so that