Authentication for large files using Content Uploader and chunk upload API?

Highlighted
First-time Contributor

Authentication for large files using Content Uploader and chunk upload API?

I'm successfully completing some uploads using the Content Uploader UI, but occasionally get a 401 unauthorized error for large files (over 1gb). 

 

Am I correct in assuming that this occurs when the file upload length outlasts the token life? If so, I don't see a refresh token endpoint or another way of extending the token expiration either before or during the upload.

 

Some details:

 

- Manually generating the JWT token server-side using PHP - no SDK is in use

- Chunk upload API is in use on content uploader, so there are separate calls to the upload endpoint

- Account settings allow up to 5gb per file

 

Can you point me in the right direction here or perhaps there is another issue causing the authentication error?

1 REPLY 1
Box Employee

Re: Authentication for large files using Content Uploader and chunk upload API?

Hi @RykerBennett, just to check, does the upload take longer than an hour?


---
Developer Advocate @ Box