9.0.0 (2026-10-01)
Features
- auth: workspace-scoped grants, MCP server permissions and identity-bound sign-in (#438) (5cd1215), closes #439
- ui: workspace scope, identities and service account sign-in in the admin UI (#439) (cddeeb9), closes #438
BREAKING CHANGES
- auth: MLflow 3.16.0 or later is required. With workspaces
enabled, grants on registered models, prompts, AI Gateway resources and
MCP servers, and patterns made with a workspace named, apply only in
their workspace. The permission API reads and writes the request
workspace's grants (defaultwhen the header is absent) and honours
workspace permissions, and experiments are judged only in their own
workspace. Existing grants are assigned a workspace at start. Gateway
group grants now take effect. Every existing service account becomes
internal: an IdP token that reached one by naming it is refused until an
administrator points the account at that provider (Kubernetes service
accounts keep working). No service account signs in interactively. MCP
server writes need per-server permissions, and existing servers stay
admin-only for changes until granted MANAGE. With more than one provider
in the registry, a bearer token is held to its bound identity, providers
cannot create accounts in another provider's email domain, and
bearer-provisioned users of a non-default provider get
<provider-id>:-namespaced groups. Accounts such a provider
bearer-provisioned before this release need
bearer_adopts_unbound_accountsor an admin rebind. See
docs/configuration.md "Upgrading: workspace-scoped grants and sign-in
rules".
🤖 Generated with Claude Code