Our application integrates with box using the web UI Elements with downscoped tokens for specific folders.
We have an issue with the Content Uploader when a user tries to upload a large file, 3-5 GB, the upload process fails silently in the background.
The failed response contains the following header:
WWW-Authenticate: Bearer realm="Service", error="invalid_token", error_description="The access token provided is invalid."
Looks like the downscoped token expires while the Content Explorer is still uploading the chunks of the file.
Is there a way to issue downscoped tokens with longer expiry or to "refresh" the token used by the Content Explorer when an error occurs while uploading?
Please sign in to leave a comment.