From 728b9b48044cf04119c0f4a9901b5171e878a7fc Mon Sep 17 00:00:00 2001 From: Valentin Cocaud Date: Mon, 17 Feb 2025 17:43:32 +0100 Subject: [PATCH] fix(docs) Fix HMAC Upstream Signature option gateway option name (#6529) --- .../gateway/other-features/security/hmac-signature.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/packages/web/docs/src/content/gateway/other-features/security/hmac-signature.mdx b/packages/web/docs/src/content/gateway/other-features/security/hmac-signature.mdx index 79fd68e54..b6b16f380 100644 --- a/packages/web/docs/src/content/gateway/other-features/security/hmac-signature.mdx +++ b/packages/web/docs/src/content/gateway/other-features/security/hmac-signature.mdx @@ -59,7 +59,7 @@ the subgraphs validating the HMAC signature. import { defineConfig } from '@graphql-hive/gateway' export const gatewayConfig = defineConfig({ - hmacUpstreamSignature: { + hmacSignature: { secret: myHMACSecret // see step 1 for the secret key } // ... @@ -195,9 +195,9 @@ Here's an example of an incoming subgraph request with the HMAC signature: ## Configuration -### `hmacUpstreamSignature` +### `hmacSignature` -The `hmacUpstreamSignature` flag allows you to customize the HMAC signing behavior in the Hive +The `hmacSignature` flag allows you to customize the HMAC signing behavior in the Hive Gateway: - `secret`: The secret key used for HMAC signing and verification. It should be a random, opaque