Please fill out the following sections to the best of your ability, it will help us investigate bugs if we have this information at the outset. Screenshots are especially helpful, so please provide those if you can.
Platform (Android, iOS, Website): Python desktop to web services
App version number, if a mobile app issue (shown under Settings): base url: /v1 , api version: 1.3.0
Browser, if a website issue (Firefox, Chrome, etc) : python client
URLs (aka web addresses) of any relevant observations or pages: https://www.inaturalist.org/oauth/token
Screenshots of what you are seeing (instructions for taking a screenshot on computers and mobile devices: https://www.take-a-screenshot.org/):
“scope”: “write login”,
Description of problem (please provide a set of steps we can use to replicate the issue, and make as many as you need.):
I am successfully trading an authorization code for an access token. I note that I get a created_at rather than the expires_in (as described in https://www.inaturalist.org/pages/api+reference#auth).
I assume the created_at is gm epoch seconds. I’d like to have the user go through another grant process a little before the token expires. What is the access token life time (in the units of your choice)?
Steps (just in case):
- client needs new access token to make secured API calls
- client sends user agent (browser) to oauth/ with authorization request
- authorization service refers authorization response to user agent (assumes user authN success and authZ grant)
- client triggered by custom protocol scheme in the response
- client posts json authorization code from response to oauth/token/
- client gets json response (which includes the bearer token)
- programmer scratches head at created_at