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
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".
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:
The text was updated successfully, but these errors were encountered: