Skip to content

Use Login5 Authentication Instead of Keymaster#311

Merged
kokarare1212 merged 1 commit intokokarare1212:mainfrom
Googolplexed0:login5-auth
Aug 17, 2025
Merged

Use Login5 Authentication Instead of Keymaster#311
kokarare1212 merged 1 commit intokokarare1212:mainfrom
Googolplexed0:login5-auth

Conversation

@Googolplexed0
Copy link
Copy Markdown
Contributor

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.

Googolplexed0 added a commit to Googolplexed0/zotify that referenced this pull request Aug 17, 2025
fix #48 (once librespot-python accepts my pull request at kokarare1212/librespot-python#311)
version bump v0.9.20
@kokarare1212
Copy link
Copy Markdown
Owner

Thank you for your contributing!

@kokarare1212 kokarare1212 merged commit 7481dca into kokarare1212:main Aug 17, 2025
4 of 5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] Error in TOKEN Authentication

2 participants