Account LInking SErvice
Tool to link accounts
The Account LInking SErvice ALISE implements the concept of site-local account linking. For this a user can log in with one local account and with any number of supported external accounts (e.g. Helmholtz-ID and Google). The local account is on at an HPC centre, which also comprises the Unix-User name.
Federated services can use this informatin whenever they need to map a federated identity to a local Unix account at a computer centre.
Examples for this are http/webDAV file access. WeDAV supports Basic Authentication, which is transported via an OIDC Access Token to convey the federated users' identity. The server needs to store the uploaded data with a specific account name, such that the same user could later access the uploaded date from e.g. computing jobs on that same server.
Alise may be used to ask users for linking their federatd identity to a local one, so that the webDAV server could find the users' corresponding local unix ID.
Installation
Account LInking SErvice is available on PyPI. Install using pip:
pip install alise
You can also install from the git repository:
git clone https://github.com/marcvs/alise
pip install -e ./alise
Dependencies
ALISE depends on gunicorn:
apt install gunicorn
Run locally (e.g. for testing)
# from the dir where alise is installed:
gunicorn alise.daemon:app -k "uvicorn.workers.UvicornWorker"
Then point your browser to http://localhost:8000
Run as a service
Nginx
We provide an nginx configuration file in alise/etc/nginx.alise
(github). Simply
copy or it to nginx like:
ln -s $PWD/alise/etc/nginx.alise /etc/nginx/sites-enabled
Systemd
We provide a systemd service file in alise/etc/alise.service
(github). Simply
copy link it to systemd like:
ln -s $PWD/alise/etc/alise.service /etc/systemd/system/
systemctl daemon-reload
systemctl enable alise.service
systemctl start alise.service
Static HTML
Place content of alise/static to place that nginx can serve as /static
Icon
Place an icon of your site into /static/<name of your sites config entry.svg
(Yep that's a bit hacky)
Configuration
ALISE is configured via a single config file. A template is provided in
alise/etc/alise.conf(github). It should be self-explanatory.
Metadata
Release files for alise 1.1.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 | Actions |
|---|---|---|---|---|
| alise-1.1.5.tar.gz | 284.8 kB | Without provenance | Details for alise-1.1.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| alise-1.1.5-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for alise-1.1.5-py2.py3-none-any.whl |
Total release size: 557.1 kB
Release files / alise-1.1.5.tar.gz
| Download URL | alise-1.1.5.tar.gz |
|---|---|
| Size | 284.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2213bf6f772ec692d913789f661feaf6ef70e63de26f4d67f3b22c6d62ab58d9
|
|
BLAKE2b-256 checksum How to use checksums |
c9f10636abeeca2e846482b29bf5d94f93a93aa78d0a146690174a3add91b122
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.3
|
Release files / alise-1.1.5-py2.py3-none-any.whl
| Download URL | alise-1.1.5-py2.py3-none-any.whl |
|---|---|
| Size | 272.3 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
73d0b6b3bd6f835f0ab39edf21ade1711c702480046745f1fbcef24f43cb72b3
|
|
BLAKE2b-256 checksum How to use checksums |
b9dc682abeb4b50b73b5d66fd327c020158f24094e7f002043122f19378e4867
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.3
|
Security for alise 1.1.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.