You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A user's login session will currently expire after 24 hours. We could leverage IMS refresh tokens to significantly increase the amount of time a user will remain logged in. High level details will most likely include:
First, determine if the asset selector, or imslib2 (which the asset selector uses for its IMS authentication) will already handle this for us. If so, we should just leverage that functionality.
If not, we may need to implement it ourselves:
Include the offline_access scope when performing authorization.
Potentially utilize onAccessTokenReceived to capture the refresh token. Hopefully the refresh token is included in the token this method provides; if not, we may need to figure out how to get it.
Persist the refresh token. Perhaps using the browser's local storage?
Use onAccessTokenExpired to read the refresh token and include it in the next authorization request?
Note that there is a refreshToken method on the IMS auth service instance returned by registerAssetsSelectorsAuthService(). So maybe all we'd need to do is call that method.
The text was updated successfully, but these errors were encountered:
A user's login session will currently expire after 24 hours. We could leverage IMS refresh tokens to significantly increase the amount of time a user will remain logged in. High level details will most likely include:
offline_access
scope when performing authorization.registerAssetsSelectorsAuthService()
. So maybe all we'd need to do is call that method.The text was updated successfully, but these errors were encountered: