mlflow-oidc-auth
OpenID Connect (OIDC) authentication and authorization plugin for MLflow.
This plugin allows you to use OIDC for user management in MLflow, enabling single sign-on (SSO) capabilities and centralized user management.
Disclaimer
This project is not affiliated with, endorsed by, or sponsored by the MLflow Project, Databricks, the Linux Foundation, or LF Projects, LLC. MLflow and related marks are trademarks of their respective owners. Maintained by Kharkevich Engineering Lab.
Features
- OIDC-based authentication for MLflow UI and API
- User management through OIDC provider
- User-level access control
- Group-based access control
- Permissions management based on regular expressions (allows or denies access to specific MLflow resources based on regular expressions and assigns permissions to users or groups)
- Support for session, JWT, and basic authentication methods
- Compatible with mlflow-client (basic auth)
Documentation
For detailed documentation, please refer to the docs. AI generated documentation is available at DeepWiki.
Quick Start
To get the full version (with entire MLflow and all dependencies), run:
python3 -m venv venv
source venv/bin/activate
python3 -m pip install mlflow-oidc-auth[full]
mlflow server --app-name oidc-auth --host 0.0.0.0 --port 8080
Webhook secret encryption key 🔐
Webhook secrets are stored encrypted in the database using a Fernet key. If you plan to use MLflow webhooks with secrets, set the encryption key in the environment variable MLFLOW_WEBHOOK_SECRET_ENCRYPTION_KEY before creating any webhooks. Generate a key with:
MLFLOW_WEBHOOK_SECRET_ENCRYPTION_KEY=$(python -c "from cryptography.fernet import Fernet; print(Fernet.generate_key().decode())")
export MLFLOW_WEBHOOK_SECRET_ENCRYPTION_KEY
Important: keep this key stable across application restarts and replicas. If the key is lost or changed after webhooks are created, previously stored secrets cannot be decrypted and will cause webhook listing to fail until you restore the original key or remove/rotate the affected webhook secrets.
Development
For development quick start, please refer to the Development and Contribution section. Contribution guidelines are available in CONTRIBUTING.md.
License
Apache 2 Licensed. For more information, please see LICENSE.
Based on MLflow basic-auth plugin
https://github.com/mlflow/mlflow/tree/master/mlflow/server/auth
1 maintainer
Metadata
1 maintainer
Release files for mlflow-oidc-auth 7.22.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| mlflow_oidc_auth-7.22.4.tar.gz | 1.3 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mlflow_oidc_auth-7.22.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.9 MB
Release files / mlflow_oidc_auth-7.22.4.tar.gz
| Download URL | mlflow_oidc_auth-7.22.4.tar.gz |
|---|---|
| Size | 1.3 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cdf6a0e3151392ea51fcfdec4f466fe68a3d7377811405855cf659ba342d8c16
|
|
BLAKE2b-256 checksum How to use checksums |
d14cfd610de5cb66f31b60271c25fd8edc32a0258791167a96b71402b1d0de2f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 28, 2026.
Transparency logRelease files / mlflow_oidc_auth-7.22.4-py3-none-any.whl
| Download URL | mlflow_oidc_auth-7.22.4-py3-none-any.whl |
|---|---|
| Size | 1.6 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bf2b1bb9e7bee61db3fc46e1e37367662f4cb88d3e6039e345650474c94caa99
|
|
BLAKE2b-256 checksum How to use checksums |
199a170a6c6f313b5507466de760803f7d3cf83c74a66ca207a46cfb585341d9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 28, 2026.
Transparency log
