Configurable Token Expiration and Regeneration for Secure File Access
Akash Sivaraman
Currently, when a PDF remains idle for a certain duration and the user attempts to interact with it, the system throws an error.
Request to enhance token management capabilities by allowing configurable expiration times and automatic regeneration of temporary API tokens when accessing files stored in the Document360 drive.
-> Ability to configure token expiration duration (e.g, 15 min, 30 min, 1 hour)
Log In
K
Kavya
Hi Overseas Mole , Akash Sivaraman,
Thank you for sharing this request.
To better understand the requirement and evaluate the possible approaches, could you please clarify a few points:
-Is this issue occurring in a public KB, private KB, or within the portal?
-Are users accessing the PDF:
Directly from the article
Via shared/download links
-What is the typical idle duration after which the error occurs?
-What would be your preferred behavior:
Longer configurable token expiry
Automatic token refresh/regeneration in the background?
Could you share the exact error message or behavior users see after the token expires?
This will help us determine whether the requirement is primarily around user experience, token lifecycle management, or security policy flexibility.
Akash Sivaraman
+ Overseas Mole