07-12-2016 08:46
07-12-2016 08:46
Hi, we're just starting to migrate over to OAuth 2.0 and noticed the 'expiresIn' value in the Access Token response (Authorization Code Grant Flow) comes back as: 28800.
The documentation says it should be 3600, so why is it coming back as 28800?
Many thanks.
Answered! Go to the Best Answer.
07-12-2016 11:09
07-12-2016 11:09
We just released this. 🙂 Documentation will be updated shortly.
Our new default lifetime for refreshable access tokens is 8 hours. You can explicitly request a 1 hour access token by setting expires_in=3600 in your access and refresh token requests.
07-12-2016 11:09
07-12-2016 11:09
We just released this. 🙂 Documentation will be updated shortly.
Our new default lifetime for refreshable access tokens is 8 hours. You can explicitly request a 1 hour access token by setting expires_in=3600 in your access and refresh token requests.
01-06-2017 07:28
01-06-2017 07:28
It appears that in API docs, the "Body Parameters" section has been updated to reflect the new 28800 default, but in the "Refreshing Tokens" section that follows, the copy reads:
When using the Authorization Code Grant flow, the access tokens have a one-hour lifetime.
Does this need to be updated as well, or am I mistaking this for something else?
01-07-2017 15:36
01-07-2017 15:36
@SteppyBob Yeah that needs to be updated since the default is 8 hours. Thanks.