mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-06 10:59:59 +00:00
kevinveenbirkenbachandClaude Opus 5
e355bbdb8b
Eight server roles declare an `mcp` RBAC role, so the platform mints roles/<app>/mcp and the administrator joins it. Open WebUI now honours those groups instead of flattening them to user/admin, and each MCP tool server is restricted to the group of the role that serves it. The grant cannot be rendered: Open WebUI matches it against a group id that insert_new_group mints as a fresh UUID, so tasks/01_mcp.yml resolves the group after the container is up and writes the grant through the admin API, the way every instance-minted credential in this repository is provisioned. Entries render disabled. An empty access_grants is not 'nobody', Open WebUI reads it as every administrator, and ENABLE_PERSISTENT_CONFIG=false makes the env authoritative again on every start. Enabling only together with the grant keeps the fallback at no access rather than too much. The provisioning account is the role-internal openwebui-api-bot, never a platform identity: OAUTH_MERGE_ACCOUNTS_BY_EMAIL ships disabled and an OIDC login whose email a local account already holds is refused, so seeding a person's address would lock them out. Known limits are documented rather than claimed away: a bare restart leaves MCP off until the next deploy, a user's roles list carries no application context so roles: [mcp] grants every deployed mcp group at once, and Open WebUI drops a stale membership only while the groups claim is non-empty. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
5 lines
168 B
YAML
5 lines
168 B
YAML
---
|
|
roles:
|
|
mcp:
|
|
description: Can drive this application through an MCP client, which acts with the credentials the deployment issued rather than the caller's own
|