You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This would go in a new mopidy auth spotify command or something, which prints the page to go to, we then redirect to mopidy.com. From there we either copy the result back to the CLI which is waiting for input, or we have the auth command spin up a HTTP server that mopidy.com redirects back to via info hidden in the state we got back.
Alternatively, the command starts up a local HTTP server and sends you there first, that redirects to Spotify, which redirects to Mopidy.com, which redirects back to the local server.
The command then uses the verifier to get a refresh token that we need to store somewhere, similar to an auth blob. From there we are good to go and can just do what we've always done.
Since we already have a major change "breaking" things switching to librespot, we might as well switch to PKCE without keeping support for the oauthclientbridge setup.
I think I have a branch with some of this coded up from years back, I'll what I can find. But if someone else wants to make PKCE work have at it :-)
The text was updated successfully, but these errors were encountered:
And we need to work out the best place to store our sensitive data. Relatedly, we currently store the spotifyaudiosrc auth blob the data directory, but that's not ideal.
https://developer.spotify.com/documentation/web-api/tutorials/code-pkce-flow has details from the Spotify side.
Essentially we want something like the following:
This would go in a new
mopidy auth spotify
command or something, which prints the page to go to, we then redirect to mopidy.com. From there we either copy the result back to the CLI which is waiting for input, or we have the auth command spin up a HTTP server that mopidy.com redirects back to via info hidden in the state we got back.Alternatively, the command starts up a local HTTP server and sends you there first, that redirects to Spotify, which redirects to Mopidy.com, which redirects back to the local server.
The command then uses the verifier to get a refresh token that we need to store somewhere, similar to an auth blob. From there we are good to go and can just do what we've always done.
Since we already have a major change "breaking" things switching to librespot, we might as well switch to PKCE without keeping support for the oauthclientbridge setup.
I think I have a branch with some of this coded up from years back, I'll what I can find. But if someone else wants to make PKCE work have at it :-)
The text was updated successfully, but these errors were encountered: