It appears that the JD Client should support refreshing of access tokens.... but the offline_access scope is not being requested so I know this has not actually been tested... ;-)
Add the offline_access scope and ensure that a refresh token is returned (currently not the case).
The access token will expire after 12 hours. So part of testing this will require that we wait 12 hours, then come back and reload the JD Status page and ensure there are no errors. But in the short term, you can also hard-code a shorter expiration time in a dev environment to test that the refresh flow is working.
Above
Test & fix if not working as currently implemented.
Test, fix.
None.
None.
None.
Fixed
1.0
Code
The refresh token seems to be working after adding offline_access to the scope and waiting 12 hours. To be sure, I will conduct another test.
Automatically closed - issue fixed for 2 weeks with no activity.