Disorganized authentication and token storage #167

Automated detection workflows and real-world observations indicate that the permission persistence system often fails to function correctly. Specific issues include:

1. Users are sometimes not prompted to log in again even after their session has expired;
2. Tokens sometimes fail to update when a user transitions from an anonymous state to a logged-in state.
   In some instances, a call to get summary returns a 403 error. The current design dictates that the system should fall back to a default, newly encoded token if the user is not logged in.

Note: Following an assessment, hard-coded tokens are permissible.