README for the Zope CMFLDAP Product CMFLDAP is designed to be run in conjunction with the LDAPUserFolder. It will replace the following tools in a CMF Site: * Membership Tool * MemberData Tool The replacements allow you to run your CMF Site with a user source backend in LDAP. The LDAPUserFolder is a replacement for a Zope user folder. It does not store its own user objects but builds them on the fly after authenticating a user against the LDAP database. For more information about the LDAPUserFolder please visit:: http://www.dataflake.org/software/ldapuserfolder/. **Requirements** In order for this product to run you will need to provide the following items: * A CMF/Plone site running off a CMF/Plone software version checked out of CVS after May 9th, 2003 or a released version released after that same date **Important Note**: If you want to allow anonymous users to join the portal then you **must** set the 'Manager DN usage' flag on the LDAPUserFolder to 'Always' and fill in a suitable DN and password as the 'Manager DN'. * A correctly configured and working LDAPUserFolder instance, software version 1.5 or higher, that is used to authenticate the CMF site. **LDAP Schema considerations** The CMF (and by extension, Plone) expect that every user has an email address. In order to make everything work correctly your LDAP user records must have a "mail" attribute, and this attribute must be set up in the "LDAP Schema" tab of your LDAPUserFolder. When you add the "mail" schema item make sure you set the "Map to Name" field to "email". Also, some places in CMF and/or Plone rely on a "fullname" attribute on the user to store the full name. LDAP usually does not have an attribute representing the full name, you can set up any attribute you desire on the LDAPUserFolder "LDAP Schema" tab and map to to "fullname". **Tested Platforms** This product has been written on and for Zope 2.6.1 and up. It is platform-independent.