MLflow Access Control (mlflow-oidc-auth)
Authentication and access control for MLflow tracking servers: single sign-on (OIDC, SAML 2.0), SCIM user and group provisioning, service accounts, and per-resource permissions for users, groups and workspaces.
It is an MLflow server plugin, installed as mlflow-oidc-auth and started with --app-name oidc-auth. The package keeps its original name; it has long since grown beyond OIDC.
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
- Single sign-on for the MLflow UI and API through any OpenID Connect provider (confidential or PKCE public clients) or SAML 2.0 identity provider, with several providers side by side
- Programmatic access: automation authenticates with short-lived workload identities — Kubernetes service-account tokens or IdP client-credentials / workload-identity tokens (JWT bearer); people using the MLflow client from a laptop or notebook use named personal access tokens (basic auth). See Programmatic access
- SCIM 2.0 provisioning of users and groups from your directory
- Permissions (READ, USE, EDIT, MANAGE) on experiments, registered models, prompts, scorers and AI Gateway resources, granted to users, groups or regex patterns, with deny by default
- Workspaces for multi-tenant isolation on a shared MLflow server
- Admin UI for users, groups, service accounts, permissions, workspaces, webhooks and trash
- Operations: server-side sessions, audit log, health probes, Redis-backed permission cache, and secrets from AWS, Azure, HashiCorp Vault or Kubernetes
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 11.0.1
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 | |
|---|---|---|---|---|
| mlflow_oidc_auth-11.0.1.tar.gz | 1.6 MB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mlflow_oidc_auth-11.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.6 MB
Release files / mlflow_oidc_auth-11.0.1.tar.gz
| Download URL | mlflow_oidc_auth-11.0.1.tar.gz |
|---|---|
| Size | 1.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1cc3dd936ea3c4272772959de7e330ac7e050bf1679942699327e224bfbbca27
|
|
BLAKE2b-256 checksum How to use checksums |
a443e9af9b87138f9b6f42a9ae573f16aeae15adb0c9d1cc3fd75b6fb2c789cb
|
| 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 Oct 20, 2026.
Transparency logRelease files / mlflow_oidc_auth-11.0.1-py3-none-any.whl
| Download URL | mlflow_oidc_auth-11.0.1-py3-none-any.whl |
|---|---|
| Size | 2.0 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6d35801b8e04020336c07c659e4a1ac88b5fe710f64fced2d6a530dd3977486a
|
|
BLAKE2b-256 checksum How to use checksums |
5fb9d93d955d7f5371bea772608a024979ad1802069c12dbce4b7e5fa2a61aea
|
| 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 Oct 20, 2026.
Transparency logSecurity for mlflow-oidc-auth 11.0.1
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for mlflow_oidc_auth-11.0.1.tar.gz
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 Oct 20, 2026.
Transparency logA 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.
