A simple program for populating a credentials.json
via Spotify's zeroconf authentication.
--name
: Name of the virtual speaker (default: "CredentialsGenerator").--path
: Target path for credentials (default:credentials.json
relative to execution).
While running on the same network as a Spotify client, it should appear as a Spotify Connect device with the given name. Select it once as an output device, and the Spotify client will transmit the required authentication blob. This blob is received by this application, written to the specified credentials path, and the application immediately exits.
This process is useful in cases where you run librespot on remote hosts on a different network (thus complicating zeroconf). As of version 3.203.235 of the Spotify eSDK, the SpConnectionLoginPassword
API has been removed.
Pre-built statically-linked binaries are available under the releases section for 64-bit Linux and Windows systems.
Install the rust toolchain (see https://rustup.rs/), and run cargo build --release
.
With default device
$ ./target/release/librespot-auth
Open Spotify and select output device: CredentialsGenerator
With precising an explicit device name
$ ./target/release/librespot-auth --name "Example Speaker"
Open Spotify and select output device: Example Speaker
Open the Spotify client from a machine on the same network as you ran this, ensuring no proxy is in use that may interfere with zeroconf (local firewall app might require turning-off momentarily). Select the speaker you just defined, i.e. "Example Speaker" or "CredentialsGenerator" in examples above, as an output device. The credentials are then saved to credentials.json
. Ensure spotifyd is stopped, i.e. sudo systemctl stop spotifyd
, copy this file to your spotifyd cache_directory
, and then start spotifyd again (sudo systemctl start spotifyd
).