Plugin for cone.app providing LDAP integration.
Features
LDAP access via node.ext.ldap
Application integration into cone.app
Integration into cone.ugm
POSIX support
Samba support
Development Setup
Prerequirements
lxml, python-ldap and openldap gets compiled, the required dev headers must be installed on the system.
On debian based systems install:
$ apt-get install -y libxml2-dev libxslt1-dev
$ apt-get install -y libsasl2-dev libssl-dev libdb-dev
Installation
cone.ldap contains a Makefile. Download or checkout package and run:
cone.ldap$ make install
Start Test LDAP server with appropriate LDIF layer:
cone.ldap$ make start-ldap-gon-10-10
Start the application:
cone.ldap$ make run-gon-10-10
and browse http://localhost:8081/. Default admin user password is admin.
The “roles” behavior in the principal form is only displayed if roles configuration is sane. The LDIF imported for test layer does not provide the roles container by default. Browse “Settings -> LDAP Roles” and perform “create roles container” action if you want to enable roles in the demo.
Note: If python_ldap fails, don’t use buildout offline mode!
Configuration and Customization
General
For customizing the plugin, make an integration package and include it in your setup.
Application configuration
To define the LDAP related configuration locations, provide the following settings in your application ini file.
# LDAP UGM backend activation
ugm.backend = ldap
# Basic LDAP server configuration
ldap.server_config = /path/to/ldap_server.xml
# LDAP UGM backend related configuration
ldap.users_config = /path/to/ldap_users.xml
ldap.groups_config = /path/to/ldap_groups.xml
ldap.roles_config = /path/to/ldap_roles.xml
Examples of these configuration file can be found at cfg folder of the source package.
UGM Default values and default value callbacks
Depending on the LDAP object classes used for users and groups, more or less attributes are required for the entries. Maybe not all of these attributes should be visible to the user. Some might even require to be computed. Therefor the plugin supports default values and default value callbacks.
Default values and callbacks are registered via factory_defaults.users, factory_defaults.groups and factory_defaults.roles.
from cone.ldap.settings import factory_defaults
The factory defaults can be static values.
factory_defaults.user['someField'] = '12345'
Default value callbacks get the principal node and id as attributes.
def some_field_callback(node, id):
return 'some computed value'
factory_defaults.user['someField'] = some_field_callback
Samba support
Example configuration to enable samba support.
from cone.ldap.settings import factory_defaults
from node.ext.ldap.ugm import posix
from node.ext.ldap.ugm import shadow
from node.ext.ldap.ugm import samba
samba.SAMBA_LOCAL_SID = 'S-1-5-21-1234567890-1234567890-1234567890'
samba.SAMBA_DEFAULT_DOMAIN = 'yourdomain'
samba.SAMBA_PRIMARY_GROUP_SID = 'S-1-5-21-1234567890-1234567890-1234567890-123'
user = factory_defaults.user
user['gidNumber'] = posix.memberGid
user['loginShell'] = posix.loginShell
user['shadowFlag'] = shadow.shadowFlag
user['shadowMin'] = shadow.shadowMin
user['shadowMax'] = shadow.shadowMax
user['shadowWarning'] = shadow.shadowWarning
user['shadowInactive'] = shadow.shadowInactive
user['shadowLastChange'] = shadow.shadowLastChange
user['shadowExpire'] = shadow.shadowExpire
user['sambaSID'] = samba.sambaUserSID
user['sambaDomainName'] = samba.sambaDomainName
user['sambaPrimaryGroupSID'] = samba.sambaPrimaryGroupSID
user['sambaAcctFlags'] = samba.sambaAcctFlags
user['sambaPwdLastSet'] = samba.sambaPwdLastSet
group = factory_defaults.group
factory_defaults.group['memberUid'] = posix.memberUid
Contributors
Robert Niederreiter (Author)
Changes
2.0.0 (2026-10-24)
Modernise the code ruff flags as outdated: u'' prefixes, class X(object). Behaviour unchanged. super(Class, self) is kept, see cone.app. [rnix]
Add qa.ruff domain to Makefile and pin the ruff rule selection in pyproject.toml, make check runs ruff check. [rnix]
Check out cone.app, cone.ugm and treibstoff from their 2.0 branches in mx.ini and pin setuptools<82.0.0. make install failed on the cone.ugm>1.99 requirement, and pyramid 2.0.2 still imports pkg_resources, which setuptools 82 removed. [rnix]
Bootstrap 5 styles.
1.1.0 (2026-02-03)
Refactor package layout to use pyproject.toml and implicit namespace packages. [rnix]
Adopt Settings UI changes from cone.app. [rnix]
Use webresource for resource registration. [rnix]
0.3 (2025-10-25)
Pin upper versions of dependencies. [rnix]
0.2 (2022-12-05)
Move users_expires_attr and users_expires_unit settings from cone.ugm, since they always have been used only for LDAP UGM backend.
0.1 (2020-07-09)
Initial release.
License
Copyright (c) 2019-2021, BlueDynamics Alliance, Austria Copyright (c) 2021-2025, Cone Contributors All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Metadata
Release files for cone.ldap 2.0.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 | Actions |
|---|---|---|---|---|
| cone_ldap-2.0.0.tar.gz | 27.6 kB | Without provenance | Details for cone_ldap-2.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cone_ldap-2.0.0-py3-none-any.whl | Python 3 | none | any | Details for cone_ldap-2.0.0-py3-none-any.whl |
Total release size: 69.6 kB
Release files / cone_ldap-2.0.0.tar.gz
| Download URL | cone_ldap-2.0.0.tar.gz |
|---|---|
| Size | 27.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
40d8b926577a5286a4551b8b30c76bc2c82be87ac48a24473dcd638517ee3a24
|
|
BLAKE2b-256 checksum How to use checksums |
2e567a7a380d319af7ed77d1d334a0d659643161bc74386d780f1ed633b5fbbe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.2
|
Release files / cone_ldap-2.0.0-py3-none-any.whl
| Download URL | cone_ldap-2.0.0-py3-none-any.whl |
|---|---|
| Size | 42.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3afb05fcb233596573c80516124e6a8c0fd9a9a2a176b4e2da9663ceddc40630
|
|
BLAKE2b-256 checksum How to use checksums |
a1a70c8de06d79e3afcd4bda5e8075d0a21e516845ac272e38b22b6f2241e790
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.2
|
Security for cone.ldap 2.0.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.