Authentication failed when using expired VCS credentials in PhpStorm

Goal: Determine whether PhpStorm can be configured to handle expired version‑control credentials automatically while maintaining least‑privilege access, without requiring the user to re‑enter credentials each time.

Currently, when a stored GitHub personal access token or similar credential expires, PhpStorm shows a generic "Authentication failed" dialog and prompts for manual re‑entry. The IDE does not refresh OAuth tokens automatically, nor does it downgrade the privileges of an already‑used token after a successful login.

Uncertainty remains about whether any hidden setting, plugin, or external authentication flow can enable silent token renewal or enforce reduced scopes after the initial authentication, thereby reducing disruption and improving security.

Specific questions:

• Is there a configuration option or plugin that allows PhpStorm to automatically refresh OAuth tokens for hosted services such as GitHub?
• Can PhpStorm be set to use a token with reduced privileges after the initial authentication, effectively implementing a least‑privilege policy for the remainder of the session?
• Does the IDE provide a mechanism to detect credential expiration and trigger a silent re‑auth flow without displaying the generic authentication failure dialog?