slapd acl
slapd olcAccess (ACLs) utility, your olcAccess in a human readable way.
Requirements
ldapsearch
Setup
pip3 install slapd_acl
Usage
using ldapi and mdb (default behaviour)
slapd_acl
specifing a base
slapd_acl -b 'olcDatabase={0}config,cn=config'
using different paramenters
usage: slapd_acl [-h] [-H H] [-Y Y] [-D D] [-w W] [-b B] [-ldif] [-enc ENC]
optional arguments:
-h, --help show this help message and exit
-H H LDAP URL
-Y Y SASL mechanism
-D D example cn:admin,dc=example,dc=org
-w W the user password
-b B Base LDAP Search
-ldif print a modify ldif
-enc ENC encoding
Modify ldif
-ldif option make the output in a ldif modify format.
Example
root@ldapmaster:~# slapd_acl -ldif
Executing:
ldapsearch -Y EXTERNAL -H ldapi:/// -b 'olcDatabase={1}mdb,cn=config' -s base 'olcAccess' -LLL
SASL/EXTERNAL authentication started
SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth
SASL SSF: 0
dn: olcDatabase={1}mdb,cn=config
changeType: modify
replace: olcAccess
olcAccess: to *
by dn.exact=gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth manage
by dn.exact="cn=admin,dc=testunical,dc=it" manage
by * break
olcAccess: to attrs=userPassword,shadowLastChange,mail
by self write
by anonymous auth
by * break
olcAccess: to *
by dn.children="ou=repl,dc=testunical,dc=it" read
by * break
olcAccess: to dn.subtree="ou=people,dc=testunical,dc=it"
by dn.children="ou=idp,dc=testunical,dc=it" read
by self read
by * break
olcAccess: to *
by anonymous auth
by * break
Authors
Giuseppe De Marco
Metadata
Release files for slapd-acl 0.2.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 |
|---|---|---|---|---|
| slapd_acl-0.2.0.tar.gz | 2.8 kB | Without provenance | Details for slapd_acl-0.2.0.tar.gz |
Release files / slapd_acl-0.2.0.tar.gz
| Download URL | slapd_acl-0.2.0.tar.gz |
|---|---|
| Size | 2.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c03fc07cfdb82a13b73f426c218f9a0ccc644f8b0aed3b8a48cf4ac061fea3a7
|
|
BLAKE2b-256 checksum How to use checksums |
cfb39ea3adc89bd7f2c1f5d90af86c1c6dbec6f9b6ecd984867a46985cea773a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/40.8.0 requests-toolbelt/0.9.1 tqdm/4.46.0 CPython/3.7.3
|
Security for slapd-acl 0.2.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.