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

Feature Request: Implement Refresh token mechanism #6

Open
DasJott opened this issue Nov 15, 2019 · 0 comments
Open

Feature Request: Implement Refresh token mechanism #6

DasJott opened this issue Nov 15, 2019 · 0 comments

Comments

@DasJott
Copy link

DasJott commented Nov 15, 2019

In your code you retrieve the token using the client_credentials grant. You also suggest to store that token for later use, which is very good.
In case that stored token once dies, there is a refresh token you can use to get a new token easily. That is OAuth2 standard. Maybe you could implement something to help people accomplish that? Of course it depends on how the token was stored...

I could think of many people not storing the token and creating a new on each API call...
Also: you would never have to care about the token anymore, as that refresh process can run automated.

For any help on that topic, see the official cleverreach documentation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant