Attachment 31012 Details for Bug 55746 – Patch for Tomcat6

Patch for Tomcat6

patch-realm.txt (text/plain), 2.84 KB, created by Cédric Couralet on 2013-11-06 06:59:41 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Cédric Couralet

Created: 2013-11-06 06:59:41 UTC

Size: 2.84 KB

patch

obsolete

>### Eclipse Workspace Patch 1.0
>#P tc6.0.x
>Index: webapps/docs/config/realm.xml
>===================================================================
>--- webapps/docs/config/realm.xml	(revision 1508339)
>+++ webapps/docs/config/realm.xml	(working copy)
>@@ -798,14 +798,30 @@
> will be attempted against each <code>Realm</code> in the order they are
> listed. Authentication against any Realm will be sufficient to authenticate
> the user.
>-
>- The CombinedRealm implementation does not support any additional
>- attributes.
>-
>+ 
> See the <a href="../realm-howto.html">Container-Managed Security
> Guide</a> for more information on setting up container managed security
> using the CombinedRealm component.
> 
>+ The CombinedRealm implementation supports the following additional
>+ attributes.
>+ 
>+ <attributes>
>+
>+ <attribute name="allRolesMode" required="false">
>+ This attribute controls how the special role name <code>*</code> is
>+ handled when processing authorization constraints in web.xml. By
>+ default, the specification compliant value of <code>strict</code> is
>+ used which means that the user must be assigned one of the roles defined
>+ in web.xml. The alternative values are <code>authOnly</code> which means
>+ that the user must be authenticated but no check is made for assigned
>+ roles and <code>strictAuthOnly</code> which means that the user must be
>+ authenticated and no check will be made for assigned roles unless roles
>+ are defined in web.xml in which case the user must be assigned at least
>+ one of those roles.
>+ </attribute>
>+ 
>+ </attributes>
> </subsection>
> 
> 
>@@ -836,7 +852,19 @@
> attributes.
> 
> <attributes>
>-
>+ <attribute name="allRolesMode" required="false">
>+ This attribute controls how the special role name <code>*</code> is
>+ handled when processing authorization constraints in web.xml. By
>+ default, the specification compliant value of <code>strict</code> is
>+ used which means that the user must be assigned one of the roles defined
>+ in web.xml. The alternative values are <code>authOnly</code> which means
>+ that the user must be authenticated but no check is made for assigned
>+ roles and <code>strictAuthOnly</code> which means that the user must be
>+ authenticated and no check will be made for assigned roles unless roles
>+ are defined in web.xml in which case the user must be assigned at least
>+ one of those roles.
>+ </attribute>
>+ 
> <attribute name="cacheRemovalWarningTime" required="false">
> If a failed user is removed from the cache because the cache is too
> big before it has been in the cache for at least this period of time (in

Actions: View

Attachments on bug 55746: 31012