-
Notifications
You must be signed in to change notification settings - Fork 53
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 'expires_in' on Token #49
Comments
Hi @tunt-04098 Thanks to spot it. |
Where is this code section? |
Note that this image https://developers.strava.com/images/authentication-2.png of the https://developers.strava.com/docs/authentication/ does not mention to store the expires_in explicitly. Maybe it's an oversight, but if you think about it the expires_at is a well defined specific time, whereas the expires_in only makes sense at the time of receiving that from the Strava back-end. If you later would send that to the Strava back-end then it would be imprecise, you'd need to offset that with the current time of sending vs the receiving time of the response... |
Hi @MrCsabaToth |
Just a note since I'm working on SUUNTO, MapMyFitness and other OAuth authentications: some OAuth servers only supply |
Hi @MrCsabaToth , i closed this issue because i am completely refactong the code and i think we should let developers to decide what to do with expires_in property. So i decided to store this value too for future sessins. thanks again for all your efforts, i am always looking forward for your valuable contributions |
Hi @dreampowder I saw there was a lot of refactoring done. Thanks for your work, I just added my comments for the record. Hopefully in the future I can contribute. |
Missing parameter 'expires_in' on Token
{
"token_type": "Bearer",
"expires_at": 1568775134,
"expires_in": 21600,
"refresh_token": "e5n567567...",
"access_token": "a4b945687g...",
"athlete": {
#{summary athlete representation}
}
}
The text was updated successfully, but these errors were encountered: