Author: olamy
Date: Tue Jan 8 23:26:45 2013
New Revision: 1430628
URL: http://svn.apache.org/viewvc?rev=1430628&view=rev
Log:
document how to use more than one Authorizer implementations
Modified:
archiva/redback/redback-site/trunk/src/site/apt/configuration.apt
Modified: archiva/redback/redback-site/trunk/src/site/apt/configuration.apt
URL:
http://svn.apache.org/viewvc/archiva/redback/redback-site/trunk/src/site/apt/configuration.apt?rev=1430628&r1=1430627&r2=1430628&view=diff
==============================================================================
--- archiva/redback/redback-site/trunk/src/site/apt/configuration.apt (original)
+++ archiva/redback/redback-site/trunk/src/site/apt/configuration.apt Tue Jan
8 23:26:45 2013
@@ -233,11 +233,15 @@ information. This can be configured wit
* ldap.config.groups.role.*(ldap group)=*(role) (mapping ldap group <->
redback role) (example: ldap.config.groups.role.archiva-admin=Archiva System
Administrator)
-** User Manager Implementation to use
+** User Manager Implementation(s) to use
* user.manager.impl=cached (since 1.4-M4: Archiva support more than one
value comma separated)
* valid values for realistic usage are 'cached' and then further
configuring the cached instance to use another underlying user manager like
ldap or the jdo one which is used by default. Placing 'ldap' here will check
with the ldap system for a fair amount of checks and would likely be a
performance issue
+** Authorizer Implementation(s) to use
+
+ * authorizer.impl=ldap,rbac (since 1.4-M4: Archiva more than one Authorizer
implementation)
+
