activedirectorytoolsforpython
This library and set of tools was designed for accessing active directory in an intuitive way compared to Microsoft Active Directory on Powershell. It is intended for Linux Operating systems and will be complimented by powershell modules for Linux to mimic the functionality of Active Directory tools for powershell that is only available on Windows.
Installing
This module requires ldap3, gssapi, and cryptography. Building the modules may require the installation of various tools and libraries on the Linux OS. Having Kerberos installed and configyred on your system is highly recommended and may be essential. Although kerberos is not needed to make the connection, it is highly advisable and easier to utilize these tools and libraries with Kerberos installed and configured.
To Build the ldap3 and gssapi python modules
Build Essentials, Development Tools, or Equivalent Must install krb5-config development libraries May require more libraries on the respective systems.
Setting up and activating the Python Virtual Environment
It is recommended to install within a Python Virtual Environment, please review your specific OS instructions to install VirtualEnv on your system.
From the directory of the repository:
python3 -m venv venv
Activating the Virtual Environment:
. venv/bin/activate
To exit the Virtual Environment:
deactivate
Installing using the setup.py
All commands should be run from the root directory of the repository.
pip install -r requirements.txt
python3 setup.py install
Installing from PyPi
pip install activedirectorytoolsforpython
Usage
This module is designed to be used from the command line to display or pipe output to other commands. It can also be used as a library to create other scripts upon in pure python. The intentions of this library was to create Powershell modules to mimic Active Directory Tools.
The examples below assume you have initialized your Kerberos tokens with kinit.
kinit bob123
If you choose you can use SIMPLE authentication with a username and password. If the username is added, Kerberso will not be used, if the password is ommitted, the user will be prompted for the password using getpass.
Python Examples
All Functions available have help, here are few examples of how to use the primary functions:
Get All ADUser Objects in your Default Domain using ldaps with Certificate with mail and sAMAccountName properties
from activedirectorytoolsforpython import *
aduser_objects = get_aduser(identity="*",cacert="./root_domain_ca.pem",properties=["mail","sAMAccountName"])
for aduser in aduser_objects:
print(aduser)
Get a Specific User from a specific Searchbase using ldaps No Verify Certificate with all properties
from activedirectorytoolsforpython import *
aduser_objects = get_aduser(identity="bob123",verify=False,properties='*')[0]
print(aduser)
Get all users with the last name of Smith using ldaps No Verify Certificate with all properties
from activedirectorytoolsforpython import *
aduser_objects = get_aduser(filter="sn=Smith",verify=False,properties='ALL')
for aduser in aduser_objects:
print(aduser)
Get all users with the last name of Smith using ldaps No Verify Certificate with all properties using ADObject
from activedirectorytoolsforpython import *
aduser_objects = get_adobject(filter="(&(objectClass=user)(sn=Smith))",verify=False,properties='ALL')
for aduser in aduser_objects:
print(aduser)
Shell Examples
Example for Getting a Group in Bash
GetADGroup -identity DnsAdmins -noverify -properties sAMAccountName,whenCreated,cn
Example for piping results into another command using the json flag
$psObj = Invoke-Expression -Command "GetADGroup -identity DnsAdmins -noverify -properties sAMAccountName,whenCreated,cn -json" | ConvertFrom-Json
Metadata
Release files for activedirectorytoolsforpython 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 | |
|---|---|---|---|---|
| activedirectorytoolsforpython-0.2.0.tar.gz | 11.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| activedirectorytoolsforpython-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 23.1 kB
Release files / activedirectorytoolsforpython-0.2.0.tar.gz
| Download URL | activedirectorytoolsforpython-0.2.0.tar.gz |
|---|---|
| Size | 11.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f54fd091d5f9edf0f9df146efef97948c7985d23a5d23b6d0de22db62e3ce7c0
|
|
BLAKE2b-256 checksum How to use checksums |
d301035b7a74323f273ce6e1ccbb053b1b73e1e0ab52d5beb7526d64d2bcbfbf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.11.2
|
Release files / activedirectorytoolsforpython-0.2.0-py3-none-any.whl
| Download URL | activedirectorytoolsforpython-0.2.0-py3-none-any.whl |
|---|---|
| Size | 11.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8d89fc6b92b8f7a97ac2ef0fd6a613be2b41c299f4d0126dd6faf2ed733c0444
|
|
BLAKE2b-256 checksum How to use checksums |
85079f71689aebd77cf5447b90caddbee553b8a029690fd7883ff4383223cd70
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.11.2
|
Security for activedirectorytoolsforpython 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.