streamtoolset
DocsChecking session…

Settings

Twitch is your sign-in identity. Spotify powers the music tools. Both authorize through OAuth; no passwords ever touch the toolset UI.

Twitch

Twitch is the sign-in identity for the entire toolset. The shared auth worker on auth.deutschmark.online handles the OAuth flow and stores a session cookie scoped to .deutschmark.online, so the same login carries across the toolset, the player widget, and the Collab Planner.

Sign out from the avatar in the top-right corner of the topbar. Re-signing in is the standard Twitch OAuth flow — no extra credentials, no app keys.

Spotify

Spotify powers Music Player. Connecting it requires a one-time paste of your own Spotify Developer credentials so the toolset can mint per-user refresh tokens against your Spotify account.

  1. Open your Spotify Developer dashboard. Go to developer.spotify.com/dashboard. Use an existing project or create a new one — Spotify caps the number of apps you can have, but one app works across the toolset.
  2. Add a redirect URI. In project settings, add https://auth.deutschmark.online/spotify/callback as a Redirect URI. Existing URIs can stay alongside it.
  3. Copy the Client ID and Client Secret. Both live on the same project settings page. Paste them into the Connections form in the toolset settings and click Connect Spotify.
  4. Authorize the OAuth flow. Spotify redirects you to grant permissions, then bounces you back. The auth worker holds a refresh token for your account from then on; the music tools just work.

Credentials are AES-GCM encrypted in KV under your Twitch identity. They never leave the worker; the toolset UI never sees the secret after submission.