Flask-AppBuilder SecurityManager for OpenIDConnect
Wrapper for flask_oidc that exposes a SecurityManager for use with any Flask-AppBuilder app.
It will allow your users to login with OpenIDConnect providers such as Auth0, Okta or Google Apps.
This is roughly inspired by the code in this stackoverflow answer. (MIT Licenced © thijsfranck)
Usage
Generic
Just override the default security manager in your Flask Appbuilder app.
from fab_oidc.security import OIDCSecurityManager
appbuilder = AppBuilder(app, db.session, security_manager_class=OIDCSecurityManager)
Airflow
Airflow provides a hook in the webserver_config.py file where you can specify a security manager class.
In webserver_config.py import the OIDCSecurityManager and set
from fab_oidc.security import AirflowOIDCSecurityManager
...
SECURITY_MANAGER_CLASS = AirflowOIDCSecurityManager
Airflow now requires that your SECURITY_MANAGER_CLASS is a subclass of AirflowSecurityManager.
Use the special AirflowOIDCSecurityManager that is only defined if you're using this library alongside Airflow.
Superset
Superset works in a a similar way. Just as in Airflow,
SECURITY_MANAGER_CLASS needs to be a subclass of SupersetSecurityManager
the config is in a file called superset_config.py and the hook is called
CUSTOM_SECURITY_MANAGER. There now exists a special
SupersetOIDCSecurityManager that is only defined if you are using this
library alongside Superset.
from fab_oidc.security import SupersetOIDCSecurityManager
...
CUSTOM_SECURITY_MANAGER = SupersetOIDCSecurityManager
Settings
The settings are the same as the flask_oidc settings, so look there for a reference.
if you're happy with flask_oidc's defaults the only thing you'll really need is something like:
OIDC_CLIENT_SECRETS = '/path/to/client_secret.json'
see the flask_oidc manual client registration docs for how to generate or write one.
OIDC Field configuration
If you like to change the default OIDC field that will be used as a username, first name and last name you can set the following env var in the shell you run your process:
export USERNAME_OIDC_FIELD='preferred_username'
export FIRST_NAME_OIDC_FIELD='given_name'
export LAST_NAME_OIDC_FIELD='family_name'
Copyright © 2018 HM Government (Ministry of Justice Digital Services). See LICENSE.txt for further details.
Metadata
Release files for fab-oidc 0.0.9
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 |
|---|---|---|---|---|
| fab_oidc-0.0.9.tar.gz | 4.0 kB | Without provenance | Details for fab_oidc-0.0.9.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| fab_oidc-0.0.9-py3-none-any.whl | Python 3 | none | any | Details for fab_oidc-0.0.9-py3-none-any.whl |
Total release size: 8.5 kB
Release files / fab_oidc-0.0.9.tar.gz
| Download URL | fab_oidc-0.0.9.tar.gz |
|---|---|
| Size | 4.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3e49b666dc15f6526c9fe0726aabed254d67e49f7e1ddbe52fa0336c4242a5f7
|
|
BLAKE2b-256 checksum How to use checksums |
a4190ff0bb46a69fcc0773be2d370dee459bf5c880929236e2c6eb23e6dc1966
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/39.2.0 requests-toolbelt/0.8.0 tqdm/4.23.4 CPython/3.6.5
|
Release files / fab_oidc-0.0.9-py3-none-any.whl
| Download URL | fab_oidc-0.0.9-py3-none-any.whl |
|---|---|
| Size | 4.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
46617f58d08ff79ac2a85e5ad96c85b57cb05ed2b22fe75d4ab81f29cfbfadf9
|
|
BLAKE2b-256 checksum How to use checksums |
fd28b7ef08bc8d75ea2fa53cd894ae4f698aab90d9de49bd98517a55e5ed281b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/39.2.0 requests-toolbelt/0.8.0 tqdm/4.23.4 CPython/3.6.5
|
Security for fab-oidc 0.0.9
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.