Flask-Multipass-CERN
This package provides the cern auth and identity providers for Flask-Multipass.
These providers are only useful if you are at CERN and intend to use Flask-Multipass with the new Keycloak-based CERN authentication infrastructure.
In its current state it also overkill if all you want to do is logging in via OIDC. If that's your
goal use the authlib multipass provider since Keycloak works perfectly fine with it.
In case you need access to arbitrary group membership information (e.g. for user-managed ACLs) and the ability to search for CERN users, then this is a good choice for you.
CERN usage details
The following permissions (requested through the application portal) are needed:
- Group membership in
authorization-service-identity-readersfor basic login and user search functionality - Group membership in
authorization-service-groups-readersfor group functionality - Tokens with group membership information (optional) - this needs to be requested directly from the authorization service team
Requesting them will most likely require you to have a professional justification.
Performance
When using group membership or user search, the library need to get an "API access" token from
keycloak which typically takes 200-300ms. Set the cache key of the multipass identity
provider configuration to the import path of a Flask-Caching instance or a function returning such
an instance, or the instance itself to enable caching of tokens (until they expire) and group
data (30 minutes).
If group membership information is included in tokens, it will be cached during login so the extra API call when checking whether a user is in a group won't be needed unless the cached data already expired.
Note
In applying the MIT license, CERN does not waive the privileges and immunities granted to it by virtue of its status as an Intergovernmental Organization or submit itself to any jurisdiction.
Metadata
Release files for Flask-Multipass-CERN 2.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| flask_multipass_cern-2.3.tar.gz | 14.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| flask_multipass_cern-2.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 23.2 kB
Release files / flask_multipass_cern-2.3.tar.gz
| Download URL | flask_multipass_cern-2.3.tar.gz |
|---|---|
| Size | 14.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cd76758446323bf59bbfe7240f8ac50009e5ad7b4f7445edd1a4fa798f92824b
|
|
BLAKE2b-256 checksum How to use checksums |
081a3be8c92ef8c449a9df7c484493d85d4b3b01f9fe18c6717945ee85e87238
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 20, 2025.
Transparency logRelease files / flask_multipass_cern-2.3-py3-none-any.whl
| Download URL | flask_multipass_cern-2.3-py3-none-any.whl |
|---|---|
| Size | 9.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d3142cdfe4217c299e7cf5ab0f0b7804f40f0f5361c0e506c7c19a35cc1d0fbb
|
|
BLAKE2b-256 checksum How to use checksums |
871da959263242ef19456ea48a4744b5c7657645c4f6b0d72060ebd722191c74
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 20, 2025.
Transparency log