Changeset 35237 for CPSLDAPSetup/trunk/README.txt
- Timestamp:
- 04/18/06 16:26:50 (4 years ago)
- Files:
-
- CPSLDAPSetup/trunk/README.txt (modified) (6 diffs)
Legend:
- Unmodified
- Added
- Removed
- Modified
- Copied
- Moved
CPSLDAPSetup/trunk/README.txt
r35176 r35237 6 6 7 7 This package provides a sample LDAP configuration in the form of an extension 8 profile for CPS 3.4 8 profile for CPS 3.4.1 9 9 10 10 The main goal of this product is to provide an example of such a configuration … … 31 31 32 32 - edit the members_ldap.xml file from profiles/default/directories/ 33 and adjust to parameters according to your own LDAP server34 configuration.33 and adjust to parameters according to your own LDAP server 34 configuration. 35 35 36 36 - Please consult other xml files in profiles/default to get the 37 37 details on how the directories will be setup. 38 38 39 39 40 Installation … … 50 51 - Go to portal_setup tool, select the CPS LDAP Setup profile and 51 52 import it. 53 - If your LDAP server is read only, may also want to additionally import the 54 CPS LDAP Setup Readonly profile (see below for more details on the readonly 55 setup). 52 56 53 57 The ldap_utils/ subfolder provides sample configuration files to setup a test … … 55 59 it, don't forget to change the passwords. 56 60 61 57 62 Structure 58 63 --------- 59 64 60 65 The default profile included in this setup changes the default ``members`` ZODB 61 directory installed by the CPSD Efault base profile by the following new compound66 directory installed by the CPSDefault base profile by the following new compound 62 67 structure of directories:: 63 68 … … 99 104 are implemented as computed fields in the members schema. 100 105 106 107 Read-only LDAP mode 108 ------------------- 109 110 If you want to plug CPS on a readonly LDAP server you should furthermore import 111 the CPSLDAPSetup "readonly_ldap" extension profile (after having first applied 112 the CPSLDAPSetup "default" extension profile). 113 114 This extension add a dynamic readonly protection to the fields that are stored 115 in the LDAP server to make it explicit to users they cannot change those values. 116 CPS specific fields (groups, roles and homeless) can still get changed (by a 117 Manager) since they do not require LDAP write access. 118 119 Furthermore, new members created from CPS are stored in the "members_zodb" 120 backing instead of "members_ldap". 121 101 122 Tuning 102 123 ------ 103 124 104 - the members_ldap and the ZODB directories are associated to the standard RAM Cache105 Manager sitting at the top of portal_directories.125 - the members_ldap and the ZODB directories are associated to the 126 standard RAM Cache Manager sitting at the top of portal_directories. 106 127 - CPSUserFolder comes with it's own built in cache set to 1s by the 107 128 CPSDefault base profile. … … 110 131 ------------ 111 132 112 - CPS >= 3.4. 0133 - CPS >= 3.4.1 113 134 http://www.cps-project.org/ 114 135 - _``python-ldap``: http://python-ldap.sf.net
