---

8.4 Re-authenticating ¶

Cases where a previously-working connector starts failing:

• Refresh token TTL elapsed. Default 30 days. ChatGPT’s connector will surface an auth error or a “reconnect” link; one click reopens the OAuth login tab and you re-enter the credentials.
• AS signing key rotated. If you (or a careless redeploy) replaced the AS state file at OAuthAsIniFile, every issued JWT becomes unverifiable. Same client-side recovery: reconnect and re-do the login flow. Avoid this in the first place by setting OAuthAsIniFile to an absolute path outside the deployed webapp; see Installation.
• Login password changed. Existing access and refresh tokens remain valid until their natural TTLs — the new password only affects new logins.
• Connector deleted and re-added. The dynamic-registration record on the AS still exists, but the client’s stored client_id is gone, so it re-registers as a new client on re-add. Old client_id entries can be pruned by editing the [client.*] sections of the AS state file when convenient.