OAuth provider connections
Configure provider OAuth connections without bypassing the shared Hoko engine.
Connection boundary
OAuth identifies and authorizes a provider connection. It does not replace Hoko authentication, authorization, usage, or rate limiting. After token exchange, the connection calls the same engine used by Dashboard, REST, CLI, and MCP.
Keep client IDs, secrets, redirect URIs, encryption keys, and provider tokens server-side. Bind state, PKCE, workspace, and callback origin before exchanging an authorization code. Revoke and disconnect must prevent later refresh from reactivating a connection.
Provider registration, redirect approval, account eligibility, and marketplace review are external gates. A local OAuth contract is not a provider receipt.
See the Apps catalog and the provider package README.