SILVER/NODEDC_PLATFORM
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

feat(n8n): add rotating provider access credential

Browse Source
This commit is contained in:
Codex
2026-07-19 10:11:56 +03:00
parent 3c5d8f6cef
commit 0611a88971
10 changed files with 408 additions and 64 deletions
Download Patch File Download Diff File Expand all files Collapse all files
packages/n8n-nodes-ndc/README.md
+10 -2
View File
@@ -30,8 +30,16 @@ The defaults are `http://external-data-plane:18106` and
`http://nodedc-module-foundry:3333`. They are provider-neutral Platform service
addresses, not workflow configuration.
The three credential types contain only one password-protected opaque
capability. Writer, reader, and Foundry capabilities are intentionally distinct.
The writer, reader, and Foundry credential types contain only one
password-protected opaque capability and are intentionally distinct. The
separate `NDC Provider Rotating Access API` credential keeps the Gelios REST access
and refresh pair inside native Engine Credentials. It exchanges the refresh
token only against the fixed Gelios refresh endpoint, persists both rotated
tokens through the supported expirable-credential lifecycle, and injects only
the current access token into provider requests. Concurrent refresh attempts in
the single-service L2 runtime are coalesced and briefly replay the same rotated
pair so a stale caller cannot immediately spend the invalidated predecessor
refresh token again.
Provider identity, product version, ontology revision, persistence policy, and
tenant scope are materialized by the receiving service from the grant. The node
never accepts them from a workflow.