Composio Auth Config Registry

Audit trail for all BYO custom auth configs created under ADR-058 Path 1. Each row represents a resolved scope gap where a provider’s default Composio OAuth app was insufficient and a custom auth config was registered.

Sessions must append a row here after completing the scope-gap-resolver runbook. Missing entries = the scope gap will recur in future sessions.

Registry

provider	auth_config_id	scopes	project	connected_user_ids	created_at	resolved_by	ADR_ref
(empty — no scope gaps resolved yet)	—	—	—	—	—	—	—

Column definitions

column	description
`provider`	Composio toolkit slug (e.g. `hubspot`, `salesforce`, `googlesheets`)
`auth_config_id`	ID returned by `composio.authConfigs.create()`
`scopes`	Comma-separated OAuth scopes granted to the BYO app
`project`	`ascend` or `kahuna_prod` (which Composio project this config belongs to)
`connected_user_ids`	`user_id` values (tenant slugs) re-connected using this auth config
`created_at`	ISO date when the auth config was created
`resolved_by`	Session/PR that created this auth config
`ADR_ref`	ADR that covers this resolution (typically ADR-058)

Infisical credential locations

BYO OAuth app credentials are stored in Infisical (project 1c1907fa-ee74-4d52-ba1a-839fc71e855d, env prod) at:

composio/oauth-apps/{provider}/client_id
composio/oauth-apps/{provider}/client_secret

Never store raw credentials here. Use Infisical references.

Adding a row

After completing the scope-gap-resolver runbook:

git add docs/composio/auth-config-registry.md
git commit -m "fix(composio): register BYO auth config for {provider} (ADR-058 Path 1)"