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

Problem with expired RefreshTokens #11

Open
JavierComas opened this issue Jan 17, 2017 · 3 comments
Open

Problem with expired RefreshTokens #11

JavierComas opened this issue Jan 17, 2017 · 3 comments

Comments

@JavierComas
Copy link

We have a client that is always on. When the uptime of the client exceeds the RefreshToken expiration time, the system hangs because it constantly tries to refresh the token and we have to restart it.

It would be nice to have a configuration parameter to set the RefreshToken expiration time, and when the time is exceeded, invalidate the token and do a new request to the oauth 2 system.

@zazoomauro
Copy link

Any update on this? I'm having the same problem. Thanks!

@dm
Copy link

dm commented Feb 11, 2017

Hi @zazoomauro and @Croma6602, I've left Sainsbury's, but since the codebase that used guzzle-oauth2-plugin has been removed before that, I doubt there will be the need to maintain this internally. And since I've left the organisation, I can't fix/push changes to this either way.
Cheers,
Dan

@zazoomauro
Copy link

@dm Thanks for your answer! So I guess this project is completely dead. That's a shame. We'll try to find something different! What about forking this project and start maintaining it properly?

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

3 participants