-
Notifications
You must be signed in to change notification settings - Fork 86
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
Missing ability to refresh token #37
Comments
@paul good point. Do you imagine then that it would catch the request error when it expired, get new token and retry? Would you be up for helping toward a PR? Thanks! |
I'm very interested in this feature, has no one taken it up since last March? |
@thebadmonkeydev unfortunately, no progress that I'm aware of. |
The more I look at this the more I feel like it belongs in heroics and not specifically in platform-api. @geemus if you agree I'll open the issue there and start working on a solution. |
1 similar comment
The more I look at this the more I feel like it belongs in heroics and not specifically in platform-api. @geemus if you agree I'll open the issue there and start working on a solution. |
I don't see a way to refresh the OAuth token once it has expired. The
#connect_oauth
function only accepts the original token, which appears to expire after a few hours. The standard OAuth handshake, and credentials provided byomniauth-heroku
include arefresh_token
attribute which may be used to automatically obtain a new token one it has expired. It would be nice if this gem accepted therefresh_token
as a param (or if it already does, document it somehow. I don't see anything in the gem docs here or in heroic.), and could automatically do the refreshed token exchange.The text was updated successfully, but these errors were encountered: