OIDC user context surfaced in chat conversations #14

Open
opened 2026-05-26 04:21:07 +00:00 by fkrebs · 0 comments
Owner

Needs clarification. Likely intent: when user chats with LobeChat/OWUI, assistant should know WHO is talking (Pocket-ID OIDC session) so it can personalise / authorise tool calls / route MCP per-user.

Options:

  1. Inject X-OIDC-Sub header → system prompt augmentation in Bifrost/OWUI middleware
  2. Per-user MCP gateway tokens (already partly done — /mcp-config?format=claude mints per-user token) extended to user-context tools
  3. KB / memory partitioned per OIDC sub claim

Ask user for concrete desired behaviour before implementing.

**Needs clarification.** Likely intent: when user chats with LobeChat/OWUI, assistant should know WHO is talking (Pocket-ID OIDC session) so it can personalise / authorise tool calls / route MCP per-user. Options: 1. Inject `X-OIDC-Sub` header → system prompt augmentation in Bifrost/OWUI middleware 2. Per-user MCP gateway tokens (already partly done — `/mcp-config?format=claude` mints per-user token) extended to user-context tools 3. KB / memory partitioned per OIDC sub claim Ask user for concrete desired behaviour before implementing.
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: fkrebs/docs#14