Converted literals to classname/interfacename docbook tags for easier indexing
This commit is contained in:
@@ -40,21 +40,21 @@
|
||||
|
||||
</programlisting></para>
|
||||
|
||||
<para>The configured <literal>AuthenticationManager</literal>
|
||||
<para>The configured <interfacename>AuthenticationManager</interfacename>
|
||||
processes each authentication request. If authentication fails, the
|
||||
configured <literal>AuthenticationEntryPoint</literal> will be used to
|
||||
configured <interfacename>AuthenticationEntryPoint</interfacename> will be used to
|
||||
retry the authentication process. Usually you will use the
|
||||
<literal>BasicProcessingFilterEntryPoint</literal>, which returns a
|
||||
401 response with a suitable header to retry HTTP Basic
|
||||
authentication. If authentication is successful, the resulting
|
||||
<literal>Authentication</literal> object will be placed into the
|
||||
<literal>SecurityContextHolder</literal>.</para>
|
||||
<interfacename>Authentication</interfacename> object will be placed into the
|
||||
<classname>SecurityContextHolder</classname>.</para>
|
||||
|
||||
<para>If the authentication event was successful, or authentication
|
||||
was not attempted because the HTTP header did not contain a supported
|
||||
authentication request, the filter chain will continue as normal. The
|
||||
only time the filter chain will be interrupted is if authentication
|
||||
fails and the <literal>AuthenticationEntryPoint</literal> is called,
|
||||
fails and the <interfacename>AuthenticationEntryPoint</interfacename> is called,
|
||||
as discussed in the previous paragraph</para>
|
||||
</section>
|
||||
</chapter>
|
||||
Reference in New Issue
Block a user