From cf6ab23349a089fee4a47b46417ef5f0d88474c6 Mon Sep 17 00:00:00 2001 From: markt Date: Fri, 22 Jul 2011 12:09:13 +0000 Subject: [PATCH] Fix https://issues.apache.org/bugzilla/show_bug.cgi?id=41498 Add info for allRolesMode git-svn-id: https://svn.apache.org/repos/asf/tomcat/trunk@1149582 13f79535-47bb-0310-9956-ffa450edef68 --- webapps/docs/changelog.xml | 4 +++ webapps/docs/config/realm.xml | 78 +++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 82 insertions(+) diff --git a/webapps/docs/changelog.xml b/webapps/docs/changelog.xml index 18c3ed938..e3b52df39 100644 --- a/webapps/docs/changelog.xml +++ b/webapps/docs/changelog.xml @@ -109,6 +109,10 @@ + 41498: Add the allRolesMode attribute to the Realm + configuration page in the documentation web application. (markt) + + 51516: Correct documentation web application to show correct system property name for changing the name of the SSO session cookie. (markt) diff --git a/webapps/docs/config/realm.xml b/webapps/docs/config/realm.xml index 9f20a40e4..5d6f387ea 100644 --- a/webapps/docs/config/realm.xml +++ b/webapps/docs/config/realm.xml @@ -107,6 +107,19 @@ + +

This attribute controls how the special role name * is + handled when processing authorization constraints in web.xml. By + default, the specification compliant value of strict is + used which means that the user must be assigned one of the roles defined + in web.xml. The alternative values are authOnly which means + that the user must be authenticated but no check is made for assigned + roles and strictAuthOnly 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.

+ +

The database username to use when establishing the JDBC connection.

@@ -208,6 +221,19 @@ + +

This attribute controls how the special role name * is + handled when processing authorization constraints in web.xml. By + default, the specification compliant value of strict is + used which means that the user must be assigned one of the roles defined + in web.xml. The alternative values are authOnly which means + that the user must be authenticated but no check is made for assigned + roles and strictAuthOnly 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.

+ +

The name of the JNDI JDBC DataSource for this Realm.

 @@ -317,6 +343,19 @@ The default value is "false".

 + +

This attribute controls how the special role name * is + handled when processing authorization constraints in web.xml. By + default, the specification compliant value of strict is + used which means that the user must be assigned one of the roles defined + in web.xml. The alternative values are authOnly which means + that the user must be authenticated but no check is made for assigned + roles and strictAuthOnly 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.

+ +

If a socket connection can not be made to the provider at the connectionURL an attempt will be made to use the @@ -554,6 +593,19 @@ + +

This attribute controls how the special role name * is + handled when processing authorization constraints in web.xml. By + default, the specification compliant value of strict is + used which means that the user must be assigned one of the roles defined + in web.xml. The alternative values are authOnly which means + that the user must be authenticated but no check is made for assigned + roles and strictAuthOnly 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.

+ +

The name of the resource that this realm will use for user, password and role information.

@@ -583,6 +635,19 @@ + +

This attribute controls how the special role name * is + handled when processing authorization constraints in web.xml. By + default, the specification compliant value of strict is + used which means that the user must be assigned one of the roles defined + in web.xml. The alternative values are authOnly which means + that the user must be authenticated but no check is made for assigned + roles and strictAuthOnly 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.

+ +

The digest algorithm used to store passwords in non-plaintext formats. Valid values are those accepted for the algorithm name by the @@ -656,6 +721,19 @@ + +

This attribute controls how the special role name * is + handled when processing authorization constraints in web.xml. By + default, the specification compliant value of strict is + used which means that the user must be assigned one of the roles defined + in web.xml. The alternative values are authOnly which means + that the user must be authenticated but no check is made for assigned + roles and strictAuthOnly 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.

+ +

The name of the application as configured in your login configuration file -- 2.11.0