Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support Client Credentials and Authorization Code Flow #8

Open
schroedermatt opened this issue Jul 2, 2018 · 0 comments
Open

Support Client Credentials and Authorization Code Flow #8

schroedermatt opened this issue Jul 2, 2018 · 0 comments
Labels
enhancement New feature or request

Comments

@schroedermatt
Copy link
Owner

schroedermatt commented Jul 2, 2018

Currently, the connector can only use a manually generated oauth token and run for 60 minutes at a time.

Why? Because spotify locks down tokens created via the client_credentials grant type to only resources unrelated to a user (which isn't much).

To gain access to a user's profile and play history, the token has to obtained via the Authorization Code flow which requires the user to click "OK" on the page a page that spotify directs you to (see link below).

Options:

  • Build small web app to authorize a user and kick off the connector task
  • Navigate through the whole Authorization Code flow is to pull in Selenium and automate the "authorization".
https://accounts.spotify.com/authorize?client_id=4e4b4261c4cc43b2ac574ab563f77a4f&response_type=code&redirect_uri=http%3A%2F%2Fkafka-demo.com&state=x4xkmn9pu3j6ukrs8n&scope=user-read-birthdate%2Cuser-read-email&show_dialog=false
@schroedermatt schroedermatt added the enhancement New feature or request label Jul 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant