Skip to content

Commit 81aae6f

Browse files
committed
docs(skills,automation): the recipes name the signed kind on main and narrow the signing gap to RSA vendors
The "Not yet" signing bullet said no auth kind signs requests. `signed` with `aliyun-acs3-hmac-sha256` or `tencentcloud-tc3-hmac-sha256` is served on the openapi and rest providers, so the Holds auth bullet names it and the gap narrows to the RSA-signing vendors (Alipay, WeChat Pay). Paid by same-file restatement cuts; the recipes stay at their 2236-token ceiling. Co-authored-by: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016WV4cwLJsQpaepqfmrTGLL
1 parent cc2c945 commit 81aae6f

1 file changed

Lines changed: 9 additions & 7 deletions

File tree

‎skills/objectstack-automation/references/integration-recipes.md‎

Lines changed: 9 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,9 @@ deployment and to the sender. Scaffolded apps list the three executors in
2929
`mcp`: `{ ok, content, structuredContent? }`), read from a later node's value slot.
3030
- `auth`, each variant with a `credentialRef`: `bearer`; `api-key` (`headerName`,
3131
default `X-API-Key`, or `paramName` for a query-string key); `basic` (`username`
32-
stays in metadata). A secret in a url path has no variant — use a
32+
stays in metadata); `signed` on `openapi` / `rest` (`scheme`
33+
`aliyun-acs3-hmac-sha256` or `tencentcloud-tc3-hmac-sha256`, `keyId`) signs each
34+
request. A secret in a url path has no variant — use a
3335
token-authenticated connector. `authentication: { token }` is refused at `os validate`.
3436
- `defineConnector`: `@objectstack/spec/integration`; `defineFlow`: `@objectstack/spec`; both register in `defineStack`.
3537

@@ -124,7 +126,7 @@ export const CarrierCallback = defineFlow({
124126
`x-objectstack-signature: t=<unix>,v1=<hex>` — HMAC-SHA256 of `<t>.<raw body>`
125127
under `CARRIER_HOOK_SECRET`. The door has no unsigned form and verifies no other
126128
scheme, so a vendor whose webhook signs its own header cannot post here today:
127-
name the gap and poll its status (recipe 1's shape) until vendor schemes verify.
129+
poll its status (recipe 1's shape) until vendor schemes verify.
128130

129131
## 5 · Vendor with no machine-readable spec — write the document by hand
130132

@@ -149,8 +151,8 @@ Each `operationId` is a named action in the flow palette and to agents;
149151

150152
- **OAuth-protected vendor** (DocuSign, Salesforce, Google): `auth` declares
151153
`oauth2` (`authorization_code` / `client_credentials`) and `app-credential`
152-
(`feishu` / `dingtalk` / `wecom`), the secret a `credentialRef`, but no server
153-
runs the grant yet: the instance is held degraded, calling no upstream. Do not
154-
park a short-lived token behind a `bearer` ref. Blocked on the outbound-OAuth card.
155-
- **Signature-authenticated vendor** (Alipay, WeChat Pay, Aliyun — RSA2 / HMAC
156-
canonical-request signing): no auth kind signs requests today; blocked on the request-signing card.
154+
(`feishu` / `dingtalk` / `wecom`), but no server runs the grant yet: the
155+
instance is held degraded, calling no upstream. Do not park a short-lived
156+
token behind a `bearer` ref. Blocked on the outbound-OAuth card.
157+
- **RSA-signing vendor** (Alipay, WeChat Pay): no `signed` scheme signs RSA yet;
158+
blocked on the request-signing card.

0 commit comments

Comments
 (0)