Re-authenticating Remote Servers

OAuth Remote Servers use access tokens to connect to the provider. Files.com refreshes expired access tokens automatically while the provider's refresh authorization remains valid. An access token's expiry or a browser session timeout does not, by itself, mean you must sign in again.

Re-authentication is needed when Files.com can no longer refresh or use the authorization. Causes include revoked access, an expired refresh token, a disabled account, or a provider policy that requires a new sign-in. Files.com displays an alert in the web interface and records authentication errors in External Logs.

Follow the link in the alert to authorize the connection again. Sign in as the account that should own the connection, and confirm that it still has access to the required remote files. After resolving the cause, save the Remote Server configuration to re-enable a disabled connection, then check the next Mount or Sync operation.

Provider token rules differ. Box refresh tokens expire after 60 days or one use; a successful refresh issues a replacement token. Dropbox offline access also uses refresh tokens to renew short-lived access tokens. Neither duration establishes a fixed schedule for manually signing in to Files.com.

Re-authentication with SSO

If the remote service uses SSO, its sign-in page may redirect you to an identity provider. The remote service controls its API authorization, while identity-provider policies can affect whether a new sign-in succeeds or is required. Ask the remote service administrator to check the authorization failure and any applicable identity policies.

When connecting a different account, use the Remote Server's Reset Authentication option. If your browser automatically selects the wrong account, sign out of that provider or use a private browser session before authorizing again.