Leihs LDAP Authenticator
LDAP based authentication handler for Leihs.
Features
-
Provides LDAP authentication for Leihs 6.x.
When users want to log in, Leihs will redirect them to this authentication handler where they can authenticate themselves using an LDAP backend
-
Automatically create new users in Leihs when they first log in.
When logging in, users must be registered with Leihs. The LDAP authenticator takes care of this automatically when the user first logs in.
-
Register or log-in via email address or username.
Users can log in via username or email address. For technical details about how LDAP users are mapped, see LDAP Username Mapping below.
-
Automatic group assignment based on LDAP attributes.
When creating the users, they can be assigned to groups in Leihs based on their LDAP attributes. Groups will be automatically created if they do not yet exist.
-
Provides automatic configuration of the Leihs authentication system.
The authenticator will automatically register itself in Leihs.
Getting Started
-
Install the tool via pip:
❯ pip install leihs-ldap-authenticator -
Download and edit the example configuration. The configuration keys are documented in the file:
❯ wget https://github.com/elan-ev/leihs-ldap-authenticator/blob/main/leihs-ldap.yml -
Run the tool:
❯ python -m leihsldap -c /path/to/leihs-ldap.ymlThe tool should automatically register itself in Leihs.
Development Version
If you want to work with the development version instead, you can just clone this repository, install the requirements and run the project from the root repository path:
❯ pip install -r requirements.txt
❯ python -m leihsldap
* Serving Flask app 'leihsldap.web'
* Debug mode: off
* Running on http://127.0.0.1:5000
Production Deployment
While you can just start and test the authenticator with the built-in web server, using this is not safe for production. For a production deployment, use a WSGI server like Gunicorn. A basic example of running this application with Gunicorn is:
❯ gunicorn --config=/path/to/gunicorn.conf.py leihsldap.web:app
For a systemd unit to turn leisldap into a service and for an example Gunicorn configuration file, take a look at the init folder:
- Example systemd unit
- Example Gunicorn configuration
Technical Notes
LDAP Username Mapping
If a user does not yet exist in Leihs, the system will always transfer the user input as an email address to the authenticator, regardless of it actually being a valid email address.
To circumvent this, the authenticator will treat the input up to the first @ character as username and use this for the LDAP login.
Once registered, Leihs will also transfer the login field which is used from there on for authentication.
Update of Data in Leihs
As a general rule, the authenticator will only ever create, but never update data in Leihs. If you want updated data in Leihs, either update this manually, or remove the resource to have it recreated with new data.
This applies to:
- Authentication system
- Groups
- Users
This also means that you can update data if you need to. For example, you can add users to additional groups without the authentication system interfering (potentially removing them again).
Support
This project is free software. It was initially developed by ELAN e.V. for Osnabrück University. We hope that this is helpful, and you can use this as well.
If you need commercial support installing this tool or want to commission further development you aren't able to do yourself, please contact the ELAN e.V.
Development
To cut a new release:
- Update the version in setup.py, commit changes, create pull request and merge
- Update the
mainbranch locally and create a release tag:git tag -s v0.4 - Push the tag upstream:
git push upstream v0.4:v0.4 - Create a new release on GitHub.
- Build Python package and upload it to pypi.org:
python setup.py sdist; twine upload dist/leihs-ldap-authenticator-0.2.tar.gz
Metadata
Release files for leihs-ldap-authenticator 0.5
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 | |
|---|---|---|---|---|
| leihs-ldap-authenticator-0.5.tar.gz | 23.9 kB | Without provenance | Details |
Release files / leihs-ldap-authenticator-0.5.tar.gz
| Download URL | leihs-ldap-authenticator-0.5.tar.gz |
|---|---|
| Size | 23.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b4952ad4b4afe9314da1df2becfa40b03570d0f87654f64e48d630653a8cf97b
|
|
BLAKE2b-256 checksum How to use checksums |
834f636ce355e99f5b3cdabcd22d350ea49c7454e1fd23cf90cddc5907c8771d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.6.0 importlib_metadata/4.6.3 pkginfo/1.7.1 requests/2.27.1 requests-toolbelt/0.9.1 tqdm/4.64.1 CPython/3.10.7
|
Security for leihs-ldap-authenticator 0.5
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.