Invalid JWT when upload large file
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 259
- Forks
- 161
- Avg merge
- 10h 33m
- Merged PRs (30d)
- 1
Description
The console application runs for 10+ hours and we are assuming between the uploads if JWT expired its getting refreshed. However, we got the attached error and suspecting the JWT expired between the chunks.
Do we need to specify something to get it refreshed?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the console application’s large-file, chunked upload path and reproduce the failure after a long-running upload. Trace how JWT expiry is handled between chunks and determine whether token refresh occurs before the next request. Done means the upload continues successfully after JWT expiration without requiring manual configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100