Globus transfer access and refresh tokens are acquired when a user first logs-in to the DataFed web app. Once acquired, DataFed refreshes the access token when needed. However, if the access or refresh token become invalid for some reason (user logs-out from globus and institutes), DataFed will continue trying to use the cached tokens which will cause Globus transfer api calls to fail. In some cases these failures are not reported to the user. The user must be notifies when this condition occurs and the message should indicate that logout/login through the web app is required (there is no other way to properly handle the OAuth process).
Globus transfer access and refresh tokens are acquired when a user first logs-in to the DataFed web app. Once acquired, DataFed refreshes the access token when needed. However, if the access or refresh token become invalid for some reason (user logs-out from globus and institutes), DataFed will continue trying to use the cached tokens which will cause Globus transfer api calls to fail. In some cases these failures are not reported to the user. The user must be notifies when this condition occurs and the message should indicate that logout/login through the web app is required (there is no other way to properly handle the OAuth process).