04-21-2016 03:26 - edited 04-21-2016 03:28
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

04-21-2016 03:26 - edited 04-21-2016 03:28
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Hi,
I'm using Authorization Code Grant Flow in oAuth2.0 Fitbit login, I'm getting code.
Using that code I get access token and refresh token from Fitbit, but expires time of access token is 3600 every time.
I want to increase expires_in time in Authorization Code Grant Flow. If anyone help me, it would be great for me and save my time.
Thanks,
Answered! Go to the Best Answer.

Accepted Solutions
04-21-2016 10:15
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



04-21-2016 10:15
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Refreshable access tokens (from the Authorization Code Grant Flow) can only have a lifetime of 1 hour.

04-21-2016 10:15
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



04-21-2016 10:15
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Refreshable access tokens (from the Authorization Code Grant Flow) can only have a lifetime of 1 hour.

06-14-2016 05:31
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

06-14-2016 05:31
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
isn't it too short? with the lifetime of 1 hour, most of the upload requests will fail with error 401 (expired_token). So there's always 1 extra request for each upload (that too if we check the expiry duration. if we don't check, and rely on error 401, it's 2 extra requests). Not so good from optimization point of view...

