Announcements

Help Wizard

Step 1

NEXT STEP

Feature Request: Granular Token Revocation and Device Disconnection for Third-Party Integrations

1. Executive Summary & Problem Description

Currently, when a Spotify account is linked to an Amazon Alexa ecosystem managed under a third-party Amazon account, the primary account holder lacks granular control to revoke access to specific external hardware devices.

Although Spotify offers a "Sign out everywhere" security feature, it explicitly excludes smart speakers and active background integrations using persistent OAuth tokens. Consequently, if a user's Spotify account becomes associated with a secondary Amazon account (e.g., in shared housing or multi-user setups), the true account owner has no mechanism within the Spotify dashboard to force-disconnect that specific Echo device or revoke access to that particular Amazon skill binding.

This creates a significant gap in user security, data privacy, and account ownership control, forcing users into unnecessary workarounds—such as full hardware factory resets or complex credential overrides—to reclaim control over their own streaming service.

2. Proposed Solution & Technical Approach

To resolve this limitation, both platforms should implement a clear session-and-device management protocol:

  • Granular OAuth Token Revocation (Spotify Dashboard):

    • Update the Spotify Account Overview > Apps section to list active external device sessions individually, rather than grouping them under generic application categories.

    • Provide an explicit "Force Disconnect Device" button next to each active integration, immediately invalidating the refresh token for that specific hardware endpoint or linked third-party profile.

  • Explicit Device Handshake Protocol (Amazon Alexa Integration):

    • Require a periodic background re-authentication handshake between the Alexa Skill and Spotify.

    • If a user updates their security credentials or revokes permissions from the Spotify side, the Amazon Echo device must immediately drop the active playback queue and display a standard "Account authorization required" prompt upon the next voice request, rather than relying on cached session tokens.

  • Account Ownership Priority:

    • Ensure that the primary owner of the Spotify account always retains master override privileges to decouple their streaming service from any secondary Amazon Household or third-party Amazon account at any time.