mirror of
https://github.com/spring-projects/spring-security.git
synced 2025-06-26 22:02:41 +00:00
Minor doc correction
This commit is contained in:
parent
c9ab463af7
commit
38dcf3859e
@ -154,8 +154,7 @@ boolean supports(Class clazz);
|
|||||||
<literal>ConfigAttribute</literal> starting with <literal>ROLE_</literal>, the
|
<literal>ConfigAttribute</literal> starting with <literal>ROLE_</literal>, the
|
||||||
<literal>RoleVoter</literal> will vote to deny access. If no
|
<literal>RoleVoter</literal> will vote to deny access. If no
|
||||||
<literal>ConfigAttribute</literal> begins with <literal>ROLE_</literal>, the voter
|
<literal>ConfigAttribute</literal> begins with <literal>ROLE_</literal>, the voter
|
||||||
will abstain. <literal>RoleVoter</literal> is case sensitive on comparisons as well as
|
will abstain. The comparisons of attributes and</para>
|
||||||
the <literal>ROLE_</literal> prefix.</para>
|
|
||||||
</section>
|
</section>
|
||||||
<section>
|
<section>
|
||||||
<title>Custom Voters</title>
|
<title>Custom Voters</title>
|
||||||
@ -190,22 +189,17 @@ boolean supports(Class clazz);
|
|||||||
that integrate with its ACL capabilities.</para>
|
that integrate with its ACL capabilities.</para>
|
||||||
<para><xref linkend="authz-after-invocation"/> illustrates Spring Security's
|
<para><xref linkend="authz-after-invocation"/> illustrates Spring Security's
|
||||||
<literal>AfterInvocationManager</literal> and its concrete implementations. <figure
|
<literal>AfterInvocationManager</literal> and its concrete implementations. <figure
|
||||||
xml:id="authz-after-invocation">
|
xml:id="authz-after-invocation"><title>After Invocation
|
||||||
<title>After Invocation Implementation</title>
|
Implementation</title><mediaobject><imageobject>
|
||||||
<mediaobject>
|
|
||||||
<imageobject>
|
|
||||||
<imagedata align="center" scalefit="1" fileref="images/AfterInvocation.gif" format="GIF"
|
<imagedata align="center" scalefit="1" fileref="images/AfterInvocation.gif" format="GIF"
|
||||||
/>
|
/>
|
||||||
</imageobject>
|
</imageobject></mediaobject></figure></para>
|
||||||
</mediaobject>
|
|
||||||
</figure></para>
|
|
||||||
<para>Like many other parts of Spring Security, <literal>AfterInvocationManager</literal> has a
|
<para>Like many other parts of Spring Security, <literal>AfterInvocationManager</literal> has a
|
||||||
single concrete implementation, <literal>AfterInvocationProviderManager</literal>, which polls
|
single concrete implementation, <literal>AfterInvocationProviderManager</literal>, which polls
|
||||||
a list of <literal>AfterInvocationProvider</literal>s. Each
|
a list of <literal>AfterInvocationProvider</literal>s. Each
|
||||||
<literal>AfterInvocationProvider</literal> is allowed to modify the return object or throw
|
<literal>AfterInvocationProvider</literal> is allowed to modify the return object or throw
|
||||||
an <literal>AccessDeniedException</literal>. Indeed multiple providers can modify the object,
|
an <literal>AccessDeniedException</literal>. Indeed multiple providers can modify the object,
|
||||||
as the result of the previous provider is passed to the next in the list. Let's now consider
|
as the result of the previous provider is passed to the next in the list.</para>
|
||||||
our ACL-aware implementations of <literal>AfterInvocationProvider</literal>.</para>
|
|
||||||
<para>Please be aware that if you're using <literal>AfterInvocationManager</literal>, you will
|
<para>Please be aware that if you're using <literal>AfterInvocationManager</literal>, you will
|
||||||
still need configuration attributes that allow the
|
still need configuration attributes that allow the
|
||||||
<classname>MethodSecurityInterceptor</classname>'s
|
<classname>MethodSecurityInterceptor</classname>'s
|
||||||
@ -222,9 +216,8 @@ boolean supports(Class clazz);
|
|||||||
<interfacename>AccessDecisionVoter</interfacename> will vote to grant access for. This
|
<interfacename>AccessDecisionVoter</interfacename> will vote to grant access for. This
|
||||||
latter (recommended) approach is usually achieved through a <literal>ROLE_USER</literal> or
|
latter (recommended) approach is usually achieved through a <literal>ROLE_USER</literal> or
|
||||||
<literal>ROLE_AUTHENTICATED</literal> configuration attribute.</para>
|
<literal>ROLE_AUTHENTICATED</literal> configuration attribute.</para>
|
||||||
|
|
||||||
<!-- TODO: Move to ACL section and add reference here -->
|
<!-- TODO: Move to ACL section and add reference here -->
|
||||||
<!--
|
<!--
|
||||||
<section xml:id="after-invocation-acl-aware">
|
<section xml:id="after-invocation-acl-aware">
|
||||||
<info>
|
<info>
|
||||||
<title>ACL-Aware AfterInvocationProviders</title>
|
<title>ACL-Aware AfterInvocationProviders</title>
|
||||||
@ -284,8 +277,7 @@ boolean supports(Class clazz);
|
|||||||
<literal>AfterInvocationProvider</literal>s.</para>
|
<literal>AfterInvocationProvider</literal>s.</para>
|
||||||
</section> -->
|
</section> -->
|
||||||
</section>
|
</section>
|
||||||
|
<!-- TODO: Move taglibs to a separate chapter which describes them all
|
||||||
<!-- TODO: Move taglibs to a separate chapter which describes them all
|
|
||||||
<section xml:id="authorization-taglibs">
|
<section xml:id="authorization-taglibs">
|
||||||
<info>
|
<info>
|
||||||
<title>Authorization Tag Libraries</title>
|
<title>Authorization Tag Libraries</title>
|
||||||
|
Loading…
x
Reference in New Issue
Block a user