SEC-184: Incorrect reference in RunAsManager reference documentation.

This commit is contained in:
Ben Alex 2006-05-23 12:07:19 +00:00
parent 92dbf836a1
commit 9e04d18cd3
1 changed files with 8 additions and 8 deletions

View File

@ -2488,20 +2488,20 @@ public boolean supports(Class clazz);</programlisting></para>
<para>The <literal>AbstractSecurityInterceptor</literal> is able to <para>The <literal>AbstractSecurityInterceptor</literal> is able to
temporarily replace the <literal>Authentication</literal> object in temporarily replace the <literal>Authentication</literal> object in
the <literal>SecurityContext</literal> and the <literal>SecurityContext</literal> and
<literal>SecurityContextHolder</literal> during the <literal>SecurityContextHolder</literal> during the secure object
<literal>SecurityInterceptorCallback</literal>. This only occurs if callback phase. This only occurs if the original
the original <literal>Authentication</literal> object was successfully <literal>Authentication</literal> object was successfully processed by
processed by the <literal>AuthenticationManager</literal> and the <literal>AuthenticationManager</literal> and
<literal>AccessDecisionManager</literal>. The <literal>AccessDecisionManager</literal>. The
<literal>RunAsManager</literal> will indicate the replacement <literal>RunAsManager</literal> will indicate the replacement
<literal>Authentication</literal> object, if any, that should be used <literal>Authentication</literal> object, if any, that should be used
during the <literal>SecurityInterceptorCallback</literal>.</para> during the <literal>SecurityInterceptorCallback</literal>.</para>
<para>By temporarily replacing the <literal>Authentication</literal> <para>By temporarily replacing the <literal>Authentication</literal>
object during a <literal>SecurityInterceptorCallback</literal>, the object during the secure object callback phase, the secured invocation
secured invocation will be able to call other objects which require will be able to call other objects which require different
different authentication and authorization credentials. It will also authentication and authorization credentials. It will also be able to
be able to perform any internal security checks for specific perform any internal security checks for specific
<literal>GrantedAuthority</literal> objects. Because Acegi Security <literal>GrantedAuthority</literal> objects. Because Acegi Security
provides a number of helper classes that automatically configure provides a number of helper classes that automatically configure
remoting protocols based on the contents of the remoting protocols based on the contents of the