[PR #311] [MERGED] Use Login5 Authentication Instead of Keymaster #315

New issue

Closed

opened 2026-02-27 08:12:42 +03:00 by kerem · 0 comments

kerem commented

2026-02-27 08:12:42 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/kokarare1212/librespot-python/pull/311
Author: @Googolplexed0
Created: 8/17/2025
Status: ✅ Merged
Merged: 8/17/2025
Merged by: @kokarare1212

Base: main ← Head: login5-auth

📝 Commits (1)

afc993f use login5 authentication instead of keymaster

📊 Changes

2 files changed (+72 additions, -28 deletions)

View changed files

📝 librespot/core.py (+66 -14)
📝 librespot/proto/spotify/login5/v3/Login5_pb2.py (+6 -14)

📄 Description

Fixes #306

It has been assumed that the previous keymaster flow for reauthenticating previous credentials has been depreciated. It is rarely used in the official client in favor of Login5.

I can't confirm it is 100% bug free, but I haven't had any issues so far. Based off a similar fix by @ermitovski here. I did a bit of cleaning and reformatting to match existing code conventions.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/kokarare1212/librespot-python/pull/311 **Author:** [@Googolplexed0](https://github.com/Googolplexed0) **Created:** 8/17/2025 **Status:** ✅ Merged **Merged:** 8/17/2025 **Merged by:** [@kokarare1212](https://github.com/kokarare1212) **Base:** `main` ← **Head:** `login5-auth` --- ### 📝 Commits (1) - [`afc993f`](https://github.com/kokarare1212/librespot-python/commit/afc993f047df2073fa256e6809c08e900cf88f09) use login5 authentication instead of keymaster ### 📊 Changes **2 files changed** (+72 additions, -28 deletions) <details> <summary>View changed files</summary> 📝 `librespot/core.py` (+66 -14) 📝 `librespot/proto/spotify/login5/v3/Login5_pb2.py` (+6 -14) </details> ### 📄 Description Fixes #306 It has been assumed that the previous keymaster flow for reauthenticating previous credentials has been depreciated. It is rarely used in the official client in favor of Login5. I can't confirm it is 100% bug free, but I haven't had any issues so far. Based off a similar fix by @ermitovski [here](https://github.com/spotizerr-dev/librespot-spotizerr/pull/6). I did a bit of cleaning and reformatting to match existing code conventions. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>