Skip to content

feat(confidentialhttp): align AuthConfig SDK with new proto shape#255

Draft
wentzeld wants to merge 3 commits into
signingExpansionfrom
rtinianov_signingExpansion
Draft

feat(confidentialhttp): align AuthConfig SDK with new proto shape#255
wentzeld wants to merge 3 commits into
signingExpansionfrom
rtinianov_signingExpansion

Conversation

@wentzeld
Copy link
Copy Markdown
Contributor

Bumps submodules/chainlink-protos to rtinianov_signedExpansion (afc1fef0), regenerates protos and SDK against the new schema, and rewrites
buildAuthConfig for the new field shape (secret_name string -> secret SecretIdentifier, StringOrSecretInput for fields that can be plain or
Vault-backed). buildAuthConfig() now returns AuthConfigJson for direct use in ConfidentialHTTPRequestJson.auth literals. Updates
src/sdk/cre/tests/confidentialhttp.test.ts — 10/10 pass.

…mps submodules/chainlink-protos to rtinianov_signedExpansion (afc1fef0), regenerates protos and SDK against the new schema, and rewrites buildAuthConfig for the new field shape (secret_name string -> secret SecretIdentifier, plus StringOrSecret for fields that can be public or secret). buildAuthConfig() now returns AuthConfigJson so callers can drop it straight into ConfidentialHTTPRequestJson.auth literals. Updates src/sdk/cre/__tests__/confidentialhttp.test.ts to match. 10/10 pass. Verified end-to-end via cre workflow simulate against chainlink-common@rtinianov_signingExpansion: a workflow exercising apiKey, apiKey-with-prefix, basic, bearer, bearer-with-custom-prefix, hmacSha256, hmacCustom-SHA512, oauth2 client_credentials, oauth2 refresh_token round-trips with the expected signed headers.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant