Ricoh LDAP Sync
Creates an address book CSV file that can be imported by Device Manager NX Lite into a Ricoh Copier.
Install
# pip install ricoh-ldap-sync
Usage
You will need the Distinguished Name or DN of a group in Active Directory where the members are users you want in the address book of the copier. You will also need a file share or something where you want scans to go.
$ ricoh-sync <Distinguished Name of group of members in Active Directory> <Path to folder where user folders will be scanned to> --csv addressbook.csv
Example
Create a CSV in this directory called addressbook.csv containing the users that are members of the group Scanner Address Book in the Groups OU.
The -f means that folders will be created for each user in the destination (\\fileserver\Scans) by first name. So this will create folders named \\fileserver\Scans\Alice, \\fileserver\Scans\Bob, etc.
$ ricoh-sync "CN=Scanner Address Book,OU=Groups,DC=example,DC=com" "\\fileserver\Scans" --csv "./addressbook.csv -f
Requires
These packages are installed automatically by pip.
- pyad
- pywin32
License
MIT
Metadata
Release files for ricoh-ldap-sync 0.1.1
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 |
|---|---|---|---|---|
| ricoh-ldap-sync-0.1.1.tar.gz | 5.2 kB | Without provenance | Details for ricoh-ldap-sync-0.1.1.tar.gz |
Release files / ricoh-ldap-sync-0.1.1.tar.gz
| Download URL | ricoh-ldap-sync-0.1.1.tar.gz |
|---|---|
| Size | 5.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
39de57235c2d9884baae1d4010bd38f20d5bfd7c6becf38885b7c128fea29461
|
|
BLAKE2b-256 checksum How to use checksums |
c22baf4bb09e6aef91131d5c5d39a514393589b1d184c2f1ac02c2783eed5b99
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/40.8.0 requests-toolbelt/0.9.1 tqdm/4.32.2 CPython/3.7.2
|
Security for ricoh-ldap-sync 0.1.1
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.