-
-
Notifications
You must be signed in to change notification settings - Fork 33
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
Refresh without client_secret // device flow and PKCE support #51
Labels
enhancement
New feature or request
Comments
hansmbakker
changed the title
Refresh without client_secret // device flow support
Refresh without client_secret // device flow and PKCE support
Jan 16, 2023
Thanks! Yeah I'd be happy to accept once it's documented, doesn't sound like it will be a major change |
What do you mean with PKCE is documented in the spotify documentation. I wrote down the calls for the device flow as well in the forum post - if needed I can clarify those. |
No I just mean in this library, that there isn't much point the feature
being available if it's not documented in an example of at least the readme.
…On Tue 17 Jan 2023, 09:05 Hans Bakker, ***@***.***> wrote:
What do you mean with documented?
PKCE is documented in the spotify documentation. I wrote down the calls
for the device flow as well in the forum post - if needed I can clarify
those.
—
Reply to this email directly, view it on GitHub
<#51 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAL5PQUTKNJRMDB6BXBU7WLWSZOFPANCNFSM6AAAAAAT5D7HQU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Aah like that, I understand. |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi @witnessmenow,
nice library! 👍
I saw that currently the token refresh calls are depending on
client_secret
:spotify-api-arduino/src/SpotifyArduino.h
Lines 234 to 235 in f0faeac
However, there are some flows where the
client_secret
is not needed - it is not needed when the refresh_token was obtained using the device flow, and I see it is also not needed when the PKCE flow was followed.Would you be open to have changes in your library where the
client_secret
is optional so that therefresh_token
can be fetched using theclient_id
only?The text was updated successfully, but these errors were encountered: