authorize link? #76

New issue

Closed

opened 2026-02-28 14:25:10 +03:00 by kerem · 2 comments

kerem commented

2026-02-28 14:25:10 +03:00

Owner

Originally created by @lnkpaulo on GitHub (Oct 18, 2024).
Original GitHub issue: https://github.com/devgianlu/go-librespot/issues/126

My config.yml

device_name: xxxxxxx
credentials:
  type: interactive
server:
  enabled: true
  address: 192.168.1.165
  port: 3678

The the ouput:

INFO[0000] api server listening on 192.168.1.165:3678   
INFO[0000] to complete authentication visit the following link: https://accounts.spotify.com/authorize?client_id=xxxxxxxxxx&code_challenge=xxxxxxxxxx&code_challenge_method=S256&redirect_uri=http%3A%2F%2F127.0.0.1%3A34753%2Flogin&response_type=code&scope=app-remote-control+playlist-modify+playlist-modify-private+playlist-modify-public+playlist-read+playlist-read-collaborative+playlist-read-private+streaming+ugc-image-upload+user-follow-modify+user-follow-read+user-library-modify+user-library-read+user-modify+user-modify-playback-state+user-modify-private+user-personalized+user-read-birthdate+user-read-currently-playing+user-read-email+user-read-play-history+user-read-playback-position+user-read-playback-state+user-read-private+user-read-recently-played+user-top-read

As we can see the uri=http%3A%2F%2F127.0.0.1%3A34753%2Flogin is not assuming the address: 192.168.1.165. Is this the expected behavior?

Thank you for the support.

Originally created by @lnkpaulo on GitHub (Oct 18, 2024). Original GitHub issue: https://github.com/devgianlu/go-librespot/issues/126 My config.yml ```yml device_name: xxxxxxx credentials: type: interactive server: enabled: true address: 192.168.1.165 port: 3678 ``` The the ouput: ``` INFO[0000] api server listening on 192.168.1.165:3678 INFO[0000] to complete authentication visit the following link: https://accounts.spotify.com/authorize?client_id=xxxxxxxxxx&code_challenge=xxxxxxxxxx&code_challenge_method=S256&redirect_uri=http%3A%2F%2F127.0.0.1%3A34753%2Flogin&response_type=code&scope=app-remote-control+playlist-modify+playlist-modify-private+playlist-modify-public+playlist-read+playlist-read-collaborative+playlist-read-private+streaming+ugc-image-upload+user-follow-modify+user-follow-read+user-library-modify+user-library-read+user-modify+user-modify-playback-state+user-modify-private+user-personalized+user-read-birthdate+user-read-currently-playing+user-read-email+user-read-play-history+user-read-playback-position+user-read-playback-state+user-read-private+user-read-recently-played+user-top-read ``` As we can see the _uri=http%3A%2F%2F127.0.0.1%3A34753%2Flogin_ is not assuming the address: 192.168.1.165. Is this the expected behavior? Thank you for the support.

kerem closed this issue

2026-02-28 14:25:10 +03:00

kerem commented

2026-02-28 14:25:11 +03:00

Author

Owner

@devgianlu commented on GitHub (Oct 20, 2024):

Yes, that is intended. The login flow is designed for the official Spotify client and therefore they have locked the redirect URI to those used by the desktop client (localhost only).

@devgianlu commented on GitHub (Oct 20, 2024): Yes, that is intended. The login flow is designed for the official Spotify client and therefore they have locked the redirect URI to those used by the desktop client (localhost only).

kerem commented

2026-02-28 14:25:11 +03:00

Author

Owner

@lnkpaulo commented on GitHub (Oct 20, 2024):

Thanks.

@lnkpaulo commented on GitHub (Oct 20, 2024): Thanks.