Open VSX Registry authentication and credential expiration handling

Extension Identity Management

VSCodium replaces the proprietary Microsoft Marketplace with the Open VSX Registry to maintain a telemetry-free environment. While standard extension installation is seamless, authentication for private registries or restricted extension scopes relies on the underlying operating system's keychain and specific OAuth flows.

Credential Lifecycle Uncertainty

There is a lack of clarity regarding how VSCodium handles expired or revoked credentials when an extension attempts to refresh its session via the Open VSX pipeline. Because VSCodium decouples from Microsoft-proprietary identity services, the behavior during a token expiration event may differ from the upstream VS Code implementation.

• Does VSCodium trigger a native OS re-authentication prompt when Open VSX credentials expire?
• Is there a documented mechanism to force a credential refresh without manually reinstalling the affected extension?