Products.CMFLDAP
NOTE: Do not install the CMFLDAP GenericSetup extension profile into a Plone site. They are meant for pure CMF sites only and will break Plone.
Bug tracker
Please post questions, bug reports or feature requests to the bug tracker at http://www.dataflake.org/tracker/
SVN version
You can retrieve the latest code from Subversion using setuptools or zc.buildout via this URL:
http://svn.dataflake.org/svn/Products.CMFLDAP/trunk#egg=Products.CMFLDAP
Debugging problems
All log messages are sent to the standard Zope event log ‘event.log’. In order to see more verbose logging output you need to increase the log level in your Zope instance’s zope.conf. See the ‘eventlog’ directive. Setting the ‘level’ key to ‘debug’ will maximize log output and may help pinpoint problems during setup and testing.
LDAP Schema considerations when used with the CMF
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 or similar, and this attribute must be set up in the “LDAP Schema” tab of your LDAPUserFolder. When you add the email schema item make sure you set the “Map to Name” field to “email”.
The attributes that show up on the join form and the personalize view are governed by the properties you ‘register’ using the ‘Member Properties’ tab in the portal_memberdata tool ZMI view, which in turn is sourced from the ‘LDAP Schema’ tab in the LDAPUserFolder ZMI view. Attributes you would like to enable for portal members must be set up on the LDAPUserFolder ‘LDAP Schema’ tab first, and then registered using the ‘Member properties’ screen in the Member data tool ZMI view.
Changelog for Products.CMFLDAP
This file contains change information for the CMFLDAP product.
1.0 (2009-02-16)
Products.CMFLDAP has been factored out of Products.LDAPUserFolder in order to streamline the LDAPUserFolder package, and to account for the difference in dependencies/versions between the LDAPUserFolder package and the CMF pieces.
Download
Metadata
Release files for Products.CMFLDAP 1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| Products.CMFLDAP-1.0.tar.gz | 41.6 kB | Without provenance | Details |
Release files / Products.CMFLDAP-1.0.tar.gz
| Download URL | Products.CMFLDAP-1.0.tar.gz |
|---|---|
| Size | 41.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
eed2f5fbecba29229176d47af9350766c2b809cafd6377954b620aff459a6cac
|
|
BLAKE2b-256 checksum How to use checksums |
e9a5d721a2d8b672c417d5d80358091065c9d64385317a384994f0f12c468d5d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for Products.CMFLDAP 1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.