Expired refresh token will now require full re-authorisation??
- 2 months ago
API support have now replied as follows:
"Refresh tokens have a limited lifetime. If a refresh token expires, you cannot refresh silently anymore, at that point you must go back through the interactive consent step to get a new authorisation code and new tokens."
Some workarounds (that require us to research and develop) were suggested to keep the refresh token alive before the 7 day expiry.
Saying "you cannot refresh silently anymore" confirms to me that this used to be possible. Clearly it is no longer possible (which is going to cause our non-admin users grief), but there has been no statement about that in the documentation about these changes. Seems to me it was/is a pretty important change.
I'm marking this as a solution, which it isn't.