Heimdall/docs/app-profiles/spotiverse.md
2026-06-02 19:25:14 +01:00

1.4 KiB

Spotiverse App Profile

Spotiverse consumes Heimdall as a managed Spotify credential authority.

Boundary

  • Heimdall owns Spotify OAuth, linked identity custody, refresh-token custody, and managed access-token projection.
  • Spotiverse owns Spotify playback polling, queue command execution, command receipts, and its CultMesh/Eve provider surface.
  • Odin, Eve, VoidBot Faces, and renderers consume the surface and command boundary; they do not receive Spotify tokens.

Providers

  • identity providers: spotify
  • entitlement sources: none
  • managed connection providers: spotify

Capabilities

  • spotify_player_read: shared capability after a linked Spotify identity.
  • spotify_queue_add: shared capability after a linked Spotify identity; Spotiverse still owns URI validation and command receipts.

Local Configuration

Heimdall needs:

GC_ACCESS_PROVIDER_SPOTIFY_CLIENT_ID=...
GC_ACCESS_PROVIDER_SPOTIFY_CLIENT_SECRET=...
GC_ACCESS_APP_SPOTIVERSE_SHARED_SECRET=...
GC_ACCESS_APP_SPOTIVERSE_BACKEND_CALLBACK_URLS=https://your-spotiverse-portal.example/auth/heimdall/callback

Spotiverse needs only the Heimdall base URL, matching app secret, and local portal callback/return URLs. The callback URL Spotiverse sends in HEIMDALL_CALLBACK_URL must exactly match one URL in Heimdall's GC_ACCESS_APP_SPOTIVERSE_BACKEND_CALLBACK_URLS allowlist unless both services are running on the same local host.