Skip to content

Commit 75abd91

Browse files
docs(adr): ADR-0143 — outbound connector auth is open tier: OAuth2 grants, vendor app-credential exchange and request signing in one declarative auth contract (#26833)
<!-- claude-projects-attribution: {"github_login":"os-steve"} --> _Requested by **Steve** · [project thread](https://claude.ai/code/project/chan_01FdL1XeUyvVNxLreh3F4Qi9?thread=cmsg_01FdL1XeUyvVNxLreh3F4Qi9BaU5Bf8FsJVKEf1GxktFtv)_ Refs #26768 Clause-②: no Metadata-protocol: none ## 维护者速读 - 改了什么:新增 ADR-0143(Proposed),把出站连接器认证整体放进开源层:OAuth2(authorization_code+PKCE+刷新、client_credentials)、飞书/钉钉/企业微信应用凭证换 token、请求签名 `signed`(封闭方案枚举);并在 ADR-0015/0018/0022/0023/0024/0097 追加带日期的修订注记(只追加,不改写原文),重新生成 ADR 索引。 - 为什么改:落实「OAuth 放开源层,先起草 ADR 修订」和「建议 1+2立卡」;#26702、#26710 的 spec/运行时/控制台切片都卡在这份记录上。 - 风险与回滚:纯文档,无代码、无 spec 变更;四个决定未答前不应合并。回滚即撤掉本 PR。注意 ADR-0015 原文其实从没划过 OAuth/企业版这条线,注记里如实写明。 - 先看:① `docs/adr/0143-outbound-connector-auth-is-open-tier.md` 的「Decisions put to the maintainer」四问(Q1 连接归属与执行身份、Q2 存储复用 better-auth account 还是独立连接对象、Q3 首批产品、Q4 首批签名方案);② 同文件 D1(哪些从企业版移出、哪些不动);③ `docs/adr/0097-declarative-connector-instances.md` 两条注记。 - 两分钟验证:`pnpm check:adr-symbol-anchors && pnpm check:adr-index`,预期两条都 0 退出、无 0143 相关告警。 - 需要你做的:在 ADR 里回答四个决定并批准 ## What changes - **New `docs/adr/0143-outbound-connector-auth-is-open-tier.md`** (Proposed). It decides, in one record: - D1, the tier move: outbound connector auth is open tier. Vault backends, curated or paid catalogs, marketplace and sandboxed stdio keep their placement. - D2, three closed authored variants: `oauth2` (`authorization_code` with mandatory S256 PKCE and refresh, `client_credentials`, MCP authorization discovery), `app-credential` (`feishu` / `dingtalk` / `wecom`) and `signed` (a closed scheme enum; a member enters only with its signer and vendor vectors). - D3: secrets stay `credentialRef`, and tokens live in an encrypted connection record, never in metadata. - D4: grant-bearing kinds resolve per dispatch, refreshing on expiry and once on a 401 with single-flight refresh. A revoked grant degrades the instance with a reason and never fails boot. - D5: a server-side Connect flow. D6: a grant is never a sign-in method. D7: the unused runtime `ConnectorOAuth2Schema` goes to the spec slice under ADR-0087. - The four maintainer decisions are stated as open questions, each with options and a recommendation, and none is decided: Q1 connection ownership / execution identity (rec. organization-shared), Q2 storage (rec. a dedicated connection object, with measured reasons `sys_account` does not fit), Q3 first products (rec. HubSpot MCP, Feishu, Alipay v3 sandbox), Q4 first signing schemes (rec. `alipay-rsa2`, `aliyun-acs3-hmac-sha256`, `tencentcloud-tc3-hmac-sha256`). - **Dated, append-only amendment notes** (each adds an `**Amended by**:` header line and a blockquote; no existing line changes): - ADR-0015: attribution only. It never drew the split others cite it for. - ADR-0018 "Out of scope (deliberately not baseline)": where the connector line was first drawn. - ADR-0022 §4: the connector half moves. The `sys_channel_account` lifecycle does not. - ADR-0023 §4. - ADR-0024 §3–§4. - ADR-0097 §3 and its "Open / enterprise line". - **`docs/adr/README.md`**, regenerated by `node scripts/adr-index.mjs` (one new row and the summary counts). - Forced test edits: none. ## Tests Docs-only diff; no package touched, so no build closure, unit test or typecheck is owed. The derived ADR gate family ran on the final head (see Verification). ## Acceptance notes - **Governing text, re-checked on `origin/main` at `0ea90c7a`.** - `git grep -n "deliberately omits OAuth2" origin/main -- docs/adr/0097-declarative-connector-instances.md` matches line 119: "The open tier deliberately omits OAuth2 from `ConnectorInstanceAuthSchema`." - `git grep -n "intentionally absent" origin/main -- packages/spec/src/shared/connector-auth.zod.ts` answers **nothing**, but the sentence is still in the file: it wraps across lines 113-114 ("OAuth2 is intentionally" / "absent (enterprise tier, ADR-0015)."). A one-line grep cannot match it. The ADR says so and names which surface each schema serves: `ConnectorOAuth2Schema` (L30-40, inside the runtime union `ConnectorAuthConfigSchema` L79-85) vs `ConnectorInstanceAuthSchema` (L158-163, authored, four static kinds). - **file:line readings behind the ADR's citations** (at `0ea90c7a`). The ADR itself cites `path#symbol`, because `check:adr-symbol-anchors` refuses line anchors in `docs/adr/**`. - `connector-auth.zod.ts`: L35 and L38 inline `clientSecret` / `refreshToken`; L99-102 `ResolvedConnectorAuth`. - `credential-resolver.ts`: L12, L21-22. - `service-automation/src/plugin.ts`: L1955 resolver pick, L1997 resolve at materialization, L2306-2337 `resolveInstanceAuth` (static kinds only). - `connector-mcp/src/mcp-provider.ts`: L63-79 `applyAuthToHeaders`, L115. - `connector-openapi/src/openapi-connector.ts`: L52 and L88-93 (`securitySchemes` typed, never read), L365 `applyAuth`. - `connector-rest/src/rest-connector.ts`: L89. - `integration/connector.zod.ts`: L1168-1192 `DeclarativeConnectorEntrySchema` (inline-secret refusal). - `sys-account.object.ts`: L183-187 (`user_id` required), L236-255 (token columns `textarea` + `internal`, not `secret`). - `auth-schema-config.ts`: L124 `AUTH_ACCOUNT_CONFIG`. - `auth-plugin.ts`: L557 `socialProviders`. - `auth-manager-plugin-list.ts`: L478-488 (oauth-provider). - `connector-imap/src/account.ts`: L60, L68-69 (`MailCredentialProvider`). - **Premise finding.** ADR-0015 contains neither "OAuth" nor "enterprise" (`grep -c -i enterprise` = 0). The enterprise placement was first drawn for connectors by ADR-0018 line 229, then repeated by 0022, 0023, 0024 and 0097. The ADR-0015 note therefore corrects the attribution and changes no decision. - **ADR-0018 line 229** also places "OAuth2 token refresh" in the enterprise tier. The seat's claim amendment 6449956947 added that file to the surface, so it carries the sixth note, and ADR-0143 lists it under Amends. - **Not in this PR:** card item 3, the cloud-repository record with a `## Provenance` pointer. This lane cannot reach the cloud repository. ADR-0143's Provenance section records that the boundary was only ever drawn in this repository (no `cloud ADR` citation in any of the six records) and that the cloud record is owed. - **Tier H.** This PR is a draft and waits for an approval from an account in `GOVERNED_APPROVERS`. The seat does not ready it, arm auto-merge or enqueue it. ## Verification <details><summary>Derived gate family, final head 6948496: 21/21 exit 0, --ran reconciles 21/21, 0 NOT-MEASURED (derived zero)</summary> `node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack` (no paths): 8 paths, 440 changed lines (under the 3000 threshold), 21 commands. Each one ran on `69484961`, with exit codes captured before any pipe: ``` 0 | node scripts/check-adr-links.mjs 0 | node scripts/check-adr-links.mjs --self-test 0 | node scripts/check-closing-keyword-parity.mjs 0 | node scripts/check-closing-keyword-parity.mjs --self-test 0 | node scripts/check-comment-mask-corpus.mjs 0 | node scripts/ci/plan-test-core-shards.mjs --self-test 0 | pnpm --filter @objectstack/lint run check:doc-formula-expressions 0 | pnpm check:adr-anchors 0 | pnpm check:adr-index 0 | pnpm check:adr-symbol-anchors 0 | pnpm check:ci-filter-parity 0 | pnpm check:closed-ceremony-text 0 | pnpm check:cross-package-test-inputs 0 | pnpm check:doc-authoring 0 | pnpm check:driver-memory-census 0 | pnpm check:gitlink-declared 0 | pnpm check:nul-bytes 0 | pnpm check:pm-governed-merges 0 | pnpm check:pm-prior-rulings 0 | pnpm check:refd-timer-probe 0 | pnpm check:watch-hint-literal ``` `--ran` (each line `command :: exit N`): "21 derived famil(ies) accounted for — 21 run, 0 NOT-MEASURED (a DERIVED zero — all 21 recorded an exit code and none of them is 3)". First-pass history: - On `a8384e3b`, `check:adr-symbol-anchors` was red with 24 `[line-anchor]` findings in ADR-0143. They were fixed in `c965eb87` by moving to `path#symbol`. - `69484961` adds the ADR-0018 note (seat review round 1); the same 21 commands re-ran there, all exit 0. - `check:doc-formula-expressions` first exited 3 (prerequisite not met, nothing measured). It went green after `pnpm exec turbo run build --filter=@objectstack/formula --filter=@objectstack/lint` under `os-verify-lock.sh` (VERDICT command-exit 0). </details> --- _Generated by [Claude Code](https://claude.ai/code/session_01ADHkmP2wqmTYar443bTqhK)_ --------- Co-authored-by: Claude <noreply@anthropic.com>
1 parent 17b5152 commit 75abd91

8 files changed

Lines changed: 437 additions & 3 deletions

‎docs/adr/0015-external-datasource-federation.md‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,15 @@
44
**Deciders**: ObjectStack Protocol Architects
55
**Builds on**: [ADR-0005](./0005-metadata-customization-overlay.md) (one Zod source of truth per metadata type)
66
**Consumers**: `@objectstack/spec`, `@objectstack/runtime`, `@objectstack/objectql`, `@objectstack/plugins/driver-sql`, `@objectstack/services/service-ai`, `@objectstack/cli`, `../objectui`
7+
**Amended by**: [ADR-0143](./0143-outbound-connector-auth-is-open-tier.md) (2026-10-27), attribution only — see the note below.
8+
9+
> **Amendment note (2026-10-27, ADR-0143) — attribution only, no decision changes.** ADR-0018,
10+
> ADR-0022, ADR-0023, ADR-0024 and ADR-0097 put OAuth2 refresh and per-tenant connection lifecycle
11+
> in the enterprise tier "per ADR-0015", and the code repeats it (`connector-auth.zod.ts`,
12+
> `credential-resolver.ts`). This record draws no such line. It names neither OAuth nor an
13+
> enterprise tier; its §10 says only that credentials are a `credentialsRef` into a secrets service.
14+
> ADR-0143 moves outbound connector auth into the open tier. Nothing here changes; cite ADR-0143,
15+
> not this record, for where connector auth sits.
716
817
> **Path note (2026-09), paths only — no decision changes.** Five paths this record cites are
918
> historical and deliberately unlinked: `packages/spec/src/data/external-lookup.zod.ts` (retired

‎docs/adr/0018-unified-node-action-registry.md‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,7 @@
44
**Deciders**: ObjectStack Protocol Architects
55
**Builds on**: [ADR-0005](./0005-metadata-customization-overlay.md) (one Zod source of truth per metadata type), [ADR-0012](./0012-notification-platform.md) (generalized outbox in `service-messaging`)
66
**Consumers**: `@objectstack/spec` (`automation/`), `@objectstack/services/service-automation`, `@objectstack/plugins/plugin-approvals`, `@objectstack/plugins/plugin-webhooks` → `service-messaging`, every plugin that registers a node executor, `../objectui` (`plugin-workflow` designer)
7+
**Amended by**: [ADR-0143](./0143-outbound-connector-auth-is-open-tier.md) (2026-10-27) — OAuth2 token refresh and the connection lifecycle leave the "Out of scope" enterprise list; see the note under that paragraph.
78

89
---
910

@@ -228,6 +229,14 @@ Because the registry starts empty, a flow that references a connector no plugin
228229

229230
Managed credentials/secret vault, OAuth2 token refresh, multi-tenant connection lifecycle, and a connector marketplace are **not** part of this mechanism — they are the enterprise tier, on the ADR-0015 precedent. The open framework ships the contract + dispatch + an in-process registry only.
230231

232+
> **Amendment note (2026-10-27, ADR-0143).** "OAuth2 token refresh" and the "multi-tenant connection
233+
> lifecycle" leave the enterprise list above: outbound connector auth is open tier. That covers
234+
> OAuth2 grants, the vendor app-credential exchange, request signing, per-dispatch refresh and the
235+
> connection record. The vault **backend** and the connector marketplace keep this paragraph's
236+
> placement. The "ADR-0015 precedent" this paragraph cites does not exist in ADR-0015's text; this
237+
> paragraph is where the line was first drawn for connectors. The registry, dispatch and the
238+
> `connector-rest` reference connector's static auth below are unchanged.
239+
231240
### Implementation checklist
232241

233242
- [x] `AutomationEngine`: connector registry (`registerConnector` / `unregisterConnector` / `resolveConnectorAction` / `getRegisteredConnectors`) + `ConnectorActionHandler` / `ConnectorActionContext` types.

‎docs/adr/0022-connectors-vs-messaging-channels.md‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,7 @@
44
**Deciders**: ObjectStack Protocol Architects
55
**Builds on**: [ADR-0012](./0012-notification-platform.md) (Messaging Platform — outbound `notify` on a generalized outbox), [ADR-0013](./0013-bidirectional-messaging.md) (Bidirectional Messaging — Slack first), [ADR-0015](./0015-external-datasource-federation.md) (open mechanism / enterprise lifecycle split), [ADR-0018](./0018-unified-node-action-registry.md) (`connector_action` as baseline generic dispatch)
66
**Consumers**: `@objectstack/spec` (`integration/`, future `messaging/`), `@objectstack/services/service-automation` (connector registry), future `@objectstack/service-messaging`, future `@objectstack/plugin-messaging-slack`, `@objectstack/connectors/*`
7+
**Amended by**: [ADR-0143](./0143-outbound-connector-auth-is-open-tier.md) (2026-10-27) — §4's connector-auth half moves to the open tier; see the note under §4.
78

89
---
910

@@ -113,6 +114,15 @@ This is the ADR-0012 "email = transport sub-system behind a channel" pattern, wi
113114

114115
A static Slack bot token is just a bearer credential, so a basic open-source Slack connector + channel is shippable in the framework; the managed-credential / OAuth-refresh / multi-tenant lifecycle is the enterprise line — the same split ADR-0015 drew for datasources and ADR-0018's addendum drew for connectors.
115116

117+
> **Amendment note (2026-10-27, ADR-0143).** For **connectors**, the "Managed OAuth2 install + token
118+
> refresh" and connection-lifecycle part of the enterprise row above is reversed: outbound connector
119+
> auth is open tier. That covers OAuth2 grants, the vendor app-credential exchange, request signing,
120+
> per-dispatch refresh and the connection record. The rest of the row keeps this record's placement:
121+
> premium connectors, marketplace, the vault backend, and the `sys_channel_account` lifecycle of a
122+
> messaging channel, which ADR-0143 does not move. A Slack channel whose `send()` delegates to the
123+
> Slack connector (§3) inherits the open connector auth. The open/enterprise line also no longer
124+
> traces to ADR-0015, which never drew it. Every other decision here stands.
125+
116126
### 5. Anti-patterns this rules out
117127

118128
- ❌ **A generic "notification connector."** Notification is a *semantic layer above* connectors, not a connector. Do not invent one.

‎docs/adr/0023-openapi-to-connector-generator.md‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,7 @@
44
**Deciders**: ObjectStack Protocol Architects
55
**Builds on**: [ADR-0015](./0015-external-datasource-federation.md) (open mechanism / enterprise lifecycle split), [ADR-0018](./0018-unified-node-action-registry.md) (`connector_action` baseline dispatch + `engine.registerConnector()`), [ADR-0022](./0022-connectors-vs-messaging-channels.md) (Connector = transport/integration mechanism; not the messaging-semantic layer)
66
**Consumers**: `@objectstack/spec` (`integration/connector.zod.ts`), `@objectstack/service-automation` (connector registry on the engine), `@objectstack/runtime` (the `GET /api/v1/automation/connectors` discovery route), new `@objectstack/connector-openapi`, the Studio flow palette
7+
**Amended by**: [ADR-0143](./0143-outbound-connector-auth-is-open-tier.md) (2026-10-27) — §4's managed-OAuth2 row moves to the open tier; see the note under §4.
78

89
---
910

@@ -116,6 +117,13 @@ The generator runs when the plugin is constructed (boot) or offline via a CLI th
116117

117118
A spec that declares OAuth2 is still importable open-source — we generate the actions and let the caller inject a static bearer token; the *managed* OAuth refresh is the enterprise line, exactly as ADR-0022 drew it for Slack.
118119

120+
> **Amendment note (2026-10-27, ADR-0143).** The "Managed OAuth2 (authorize + token refresh) …
121+
> per-tenant connection lifecycle" row is reversed: outbound connector auth is open tier. The
122+
> generator gains the matching inputs: an `oauth2` `securitySchemes` entry is mapped rather than
123+
> left for the caller to replace with a static bearer token, and a declarative instance may also
124+
> declare an `app-credential` or `signed` auth kind. The vault backend and the curated / paid
125+
> catalog row keep this record's placement. Every other decision here stands.
126+
119127
### 5. Anti-patterns this rules out
120128

121129
- ❌ **A bespoke importer per vendor.** If the vendor publishes OpenAPI, the generic generator covers it; don't hand-roll.

‎docs/adr/0024-mcp-connectors.md‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,7 @@
44
**Deciders**: ObjectStack Protocol Architects
55
**Builds on**: [ADR-0011](./0011-actions-as-ai-tools.md) (actions as AI tools), [ADR-0015](./0015-external-datasource-federation.md) (open mechanism / enterprise lifecycle split), [ADR-0018](./0018-unified-node-action-registry.md) (`connector_action` baseline dispatch + connector registry), [ADR-0022](./0022-connectors-vs-messaging-channels.md) (Connector = transport/integration mechanism), [ADR-0023](./0023-openapi-to-connector-generator.md) (OpenAPI → Connector generator)
66
**Consumers**: `@objectstack/spec` (`integration/connector.zod.ts`), `@objectstack/service-automation` (connector registry on the engine), `@objectstack/runtime` (the `GET /api/v1/automation/connectors` discovery route), new `@objectstack/connector-mcp`, `@objectstack/service-ai` (the same MCP tools double as AI tools, ADR-0011), the Studio flow palette
7+
**Amended by**: [ADR-0143](./0143-outbound-connector-auth-is-open-tier.md) (2026-10-27) — the MCP authorization flow and per-connection grants are open tier; see the note under §4.
78

89
---
910

@@ -113,6 +114,15 @@ An MCP server owns its own auth (e.g. a GitHub token passed via `env` on the std
113114

114115
Running a community MCP server with an operator-provided token is open-source; *managing* those servers and their secrets at scale, multi-tenant, is the enterprise line — the identical split ADR-0022/0023 drew.
115116

117+
> **Amendment note (2026-10-27, ADR-0143).** This record names no OAuth, but its "per-tenant MCP
118+
> connection lifecycle" row is where an OAuth-protected http server's grant would fall, and that
119+
> part is reversed. The MCP authorization flow on the http transport is open tier: protected-resource
120+
> discovery, dynamic client registration, PKCE, and refresh per dispatch against a per-connection
121+
> grant. §3's "we do not model the upstream's auth in `ConnectorSchema`" is amended to match: a
122+
> declarative instance's `auth` may now be `oauth2`. The curated registry, one-click install, the
123+
> vault backend, sandboxed stdio execution and the paid catalog keep this record's placement. Every
124+
> other decision here stands.
125+
116126
### 5. Anti-patterns this rules out
117127

118128
- ❌ **A new flow node for MCP.** MCP tools are dispatched through the existing `connector_action` node; no `mcp_call` node.

‎docs/adr/0097-declarative-connector-instances.md‎

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,7 @@
55
**Builds on**: [ADR-0015](./0015-external-datasource-federation.md) (open mechanism / enterprise lifecycle split), [ADR-0018](./0018-unified-node-action-registry.md) (`connector_action` baseline dispatch + `engine.registerConnector()`), [ADR-0022](./0022-connectors-vs-messaging-channels.md) (Connector = transport/integration mechanism), [ADR-0023](./0023-openapi-to-connector-generator.md) (OpenAPI → Connector generator), [ADR-0024](./0024-mcp-connectors.md) (MCP servers as connectors)
66
**Tracking**: framework#2977 (supersedes the interim descriptor-only contract from framework#2612)
77
**Consumers**: `@objectstack/spec` (`stack.zod.ts`, `integration/connector.zod.ts`), `@objectstack/service-automation` (boot audit → provider binding), `@objectstack/connector-openapi`, `@objectstack/connector-mcp`, `@objectstack/connector-rest`, the Studio flow palette, AI authoring (stack generation)
8+
**Amended by**: [ADR-0143](./0143-outbound-connector-auth-is-open-tier.md) (2026-10-27) — OAuth2, the vendor app-credential exchange and request signing join `ConnectorInstanceAuthSchema` in the open tier, and those kinds resolve per dispatch; see the notes under §3 and under "Open / enterprise line".
89

910
---
1011

@@ -70,6 +71,14 @@ A connector plugin (e.g. `@objectstack/connector-openapi`) registers a **provide
7071

7172
`credentialRef` resolves through the secrets service at materialization time. Inline secrets in stack metadata are rejected at authoring/publish (lint + schema). Per the ADR-0015 line: static credentials resolved from env/config are **open**; managed vaulting, OAuth2 refresh, and per-tenant connection lifecycle are **enterprise**.
7273

74+
> **Amendment note (2026-10-27, ADR-0143).** OAuth2 refresh and the per-connection lifecycle are
75+
> open tier now. The vaulting **backend** keeps this placement. `credentialRef` stays the only
76+
> way an author names a secret, and inline secrets stay refused at publish. What changes is *when*
77+
> resolution happens, for the new grant-bearing kinds only: `oauth2` and `app-credential` resolve a
78+
> live token per dispatch, refreshing on expiry and once on a `401`, and `signed` resolves its
79+
> signer per dispatch. Their tokens live in a connection record, never in metadata. The four static
80+
> kinds still resolve once, at materialization.
81+
7382
### 4. Two-sources-of-truth rule
7483

7584
If a provider-bound instance and a plugin-registered connector share a `name`, boot fails with a naming-conflict error — there is no precedence, because silent precedence is how drift hides. (Plain descriptors sharing a live connector's name stay legal: the descriptor is catalog metadata *about* the live connector.)
@@ -118,6 +127,20 @@ If a provider-bound instance and a plugin-registered connector share a `name`, b
118127
- **Open source:** the `rest` / `openapi` / `mcp` provider factories; **static** auth (`none` / `api-key` / `basic` / `bearer`); `credentialRef` resolved from **environment variables** (`defaultEnvCredentialResolver`) — the degraded-but-honest story for environments with no managed secrets service.
119128
- **Enterprise:** managed credential **vaulting** and OAuth2 authorization-code/refresh lifecycle (inject a vault-backed `CredentialResolver` via `AutomationServicePluginOptions.credentialResolver` — no change to the materialization path), plus per-tenant connection lifecycle. The open tier deliberately omits OAuth2 from `ConnectorInstanceAuthSchema`.
120129

130+
> **Amendment note (2026-10-27, ADR-0143).** The enterprise bullet above is reversed except for its
131+
> vaulting backend: a vault-backed `CredentialResolver` injected through
132+
> `AutomationServicePluginOptions.credentialResolver` is still the extension point. The open tier
133+
> now adds three variants to `ConnectorInstanceAuthSchema`, each with a closed enum refused at
134+
> publish when unknown:
135+
> - `oauth2`: `authorization_code` with PKCE and refresh, or `client_credentials`;
136+
> - `app-credential`: Feishu, DingTalk or WeCom;
137+
> - `signed`: a closed scheme enum.
138+
>
139+
> It also adds the connection record and the Connect / Reconnect flow. An instance whose grant is
140+
> missing or revoked degrades under the upstream-availability rules below, with a reason that names
141+
> the grant, and never fails a boot. The open-tier bullet's "static auth" list stays true of what
142+
> resolves at materialization.
143+
121144
### Runtime reconcile (follow-up, landed)
122145

123146
Materialization is no longer boot-only. `materializeDeclaredConnectors` is a

0 commit comments

Comments
 (0)