Skip to content

Service-role media upload needs a user account a service-role caller does not have #167

Description

@HMarzban

Problem

POST /api/plugins/hypermultimedia/:documentId requires a verified user (apps/hocuspocus.server/src/api/routers/hypermultimedia.router.ts:30-36). The controller then spends that user on the private-document and read-only gates.

A service-role caller has no user. So an automated media upload has to create a real account first, and a failed cleanup leaves that account behind.

What to decide

Whether a service-role bearer may skip the user requirement on a public, unlocked document. The gate here is about access, not about identity.

Acceptance

  • A yes or no is recorded in this issue.
  • On a yes, an upload to a public unlocked document succeeds with no user account created.

Notes

A service-role write carries the operation, never a person. Do not solve this by minting a bot user row.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions