mosaic/stack
1
0
Fork 0
Code Issues 10 Pull Requests Actions Packages Projects Releases 2 Wiki Activity

Create UserCredential Prisma model with RLS policies #355

New Issue
Closed
opened 2026-02-07 17:11:43 +00:00 by jason.woltje · 0 comments
jason.woltje commented 2026-02-07 17:11:43 +00:00
Owner
Copy Link

Phase 3a - User Credential Storage

Problem

There is no database model for users to store their own API keys, git tokens, or OAuth tokens for integrations. Users need a secure, RLS-protected table to manage personal and workspace-scoped credentials.

Requirements

  1. Create UserCredential Prisma model with encrypted value storage
  2. Add CredentialType enum (API_KEY, OAUTH_TOKEN, ACCESS_TOKEN, SECRET, PASSWORD, CUSTOM)
  3. Add CredentialScope enum (USER, WORKSPACE, SYSTEM)
  4. Add RLS policies: USER-scoped visible only to owner, WORKSPACE-scoped visible to workspace admins, SYSTEM-scoped via admin bypass
  5. Extend EntityType enum with CREDENTIAL
  6. Extend ActivityAction enum with CREDENTIAL_CREATED, CREDENTIAL_ACCESSED, CREDENTIAL_ROTATED, CREDENTIAL_REVOKED
  7. Add relations to User and Workspace models

Model Design

UserCredential fields:

  • id (UUID)
  • userId (FK to User)
  • workspaceId (optional FK to Workspace)
  • name (display name, e.g. GitHub
## Phase 3a - User Credential Storage ### Problem There is no database model for users to store their own API keys, git tokens, or OAuth tokens for integrations. Users need a secure, RLS-protected table to manage personal and workspace-scoped credentials. ### Requirements 1. Create UserCredential Prisma model with encrypted value storage 2. Add CredentialType enum (API_KEY, OAUTH_TOKEN, ACCESS_TOKEN, SECRET, PASSWORD, CUSTOM) 3. Add CredentialScope enum (USER, WORKSPACE, SYSTEM) 4. Add RLS policies: USER-scoped visible only to owner, WORKSPACE-scoped visible to workspace admins, SYSTEM-scoped via admin bypass 5. Extend EntityType enum with CREDENTIAL 6. Extend ActivityAction enum with CREDENTIAL_CREATED, CREDENTIAL_ACCESSED, CREDENTIAL_ROTATED, CREDENTIAL_REVOKED 7. Add relations to User and Workspace models ### Model Design UserCredential fields: - id (UUID) - userId (FK to User) - workspaceId (optional FK to Workspace) - name (display name, e.g. GitHub
jason.woltje added this to the M9-CredentialSecurity (0.0.9) milestone 2026-02-07 17:11:43 +00:00
jason.woltje added the databasesecuritydatabasep1 labels 2026-02-07 17:11:43 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
ai
AI/LLM integration
 api
Backend/API work
 api
auth
Authentication
 database
database
Database/schema work
 devops
Docker/deployment
 docs
Documentation
 frontend
graph
knowledge-module
migration
Data migration
 orchestrator
Orchestrator service (apps/orchestrator/)
 p0
Critical priority
 p1
High priority
 p2
Medium priority
 p3
Low priority
 performance
Performance work
 phase-1
phase-2
phase-3
phase-4
phase-5
plugin
MoltBot plugin work
 search
security
Security-related
 setup
Initial setup
 testing
Testing/QA
 web
Frontend work
No Label database database p1 security
Milestone
No items
No Milestone M9-CredentialSecurity (0.0.9)
Projects
Clear projects
No project
Assignees
Clear assignees
jason.woltje
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaic/stack#355
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?