Make Token Expiration Instructions clear in upgrade docs
Background
This was mentioned as part of the ongoing effort to better inform customers about token expiry in a proactive manner.
Request
Add clarity to the upgrade documentation page(s) about upgrades - OPEN QUESTION - should we include as part of 16.x upgrade, 17.x upgrade, or both? by:
- Explaining the token expiration changes (that for those with no date, expiration set for 1 year from date of upgrade - link to deprecation and removal but also make it clear that there are steps they can take to lessen impact using the troubleshooting guide
Edited by Hannah Sutor