authorization warnings and config naming (#3162)

Author: khadni

reports/llms-report.json

@@ -1,22 +1,22 @@
 {
-  "startedAt": "2025-11-11T18:30:56.374Z",
+  "startedAt": "2025-11-11T23:46:50.901Z",
   "siteBase": "https://docs.chain.link",
   "sections": [
     {
       "section": "cre-go",
       "pagesProcessed": 84,
       "outputPath": "src/content/cre/llms-full-go.txt",
-      "bytes": 631069,
-      "prevBytes": 631094,
-      "deltaBytes": -25
+      "bytes": 631240,
+      "prevBytes": 631069,
+      "deltaBytes": 171
     },
     {
       "section": "cre-ts",
       "pagesProcessed": 79,
       "outputPath": "src/content/cre/llms-full-ts.txt",
-      "bytes": 586483,
-      "prevBytes": 586508,
-      "deltaBytes": -25
+      "bytes": 586661,
+      "prevBytes": 586483,
+      "deltaBytes": 178
     },
     {
       "section": "vrf",
@@ -123,5 +123,5 @@
       "deltaBytes": 0
     }
   ],
-  "finishedAt": "2025-11-11T18:31:00.312Z"
+  "finishedAt": "2025-11-11T23:46:54.854Z"
 }

src/content/cre/guides/workflow/using-triggers/http-trigger/configuration-go.mdx

@@ -58,7 +58,7 @@ func InitWorkflow(config *Config, logger *slog.Logger, secretsProvider cre.Secre
     authorizedKeys := []*http.AuthorizedKey{
         {
             Type:      http.KeyType_KEY_TYPE_ECDSA_EVM,
-            PublicKey: config.HTTPPublicKey,
+            PublicKey: config.AuthorizedEVMAddress,
         },
     }
 

src/content/cre/guides/workflow/using-triggers/http-trigger/configuration-ts.mdx

@@ -33,7 +33,7 @@ You create an HTTP trigger by calling the `HTTPCapability.trigger()` method. Its
 import { cre, type Runtime, type HTTPPayload, Runner } from "@chainlink/cre-sdk"
 
 type Config = {
-  httpPublicKey: string
+  authorizedEVMAddress: string
 }
 
 // Callback function that runs when an HTTP request is received
@@ -52,7 +52,7 @@ const initWorkflow = (config: Config) => {
         authorizedKeys: [
           {
             type: "KEY_TYPE_ECDSA_EVM",
-            publicKey: config.httpPublicKey,
+            publicKey: config.authorizedEVMAddress,
           },
         ],
       }),

src/content/cre/guides/workflow/using-triggers/http-trigger/overview-go.mdx

@@ -24,10 +24,11 @@ When you deploy a workflow with an HTTP trigger:
 1. **CRE validates the signature** against your configured `authorizedKeys`
 1. **If authorized**, your workflow callback executes with the request payload
 
-<Aside type="note" title="Security by design">
+<Aside type="caution" title="Authorization required for deployed workflows">
   For **deployed workflows**, HTTP triggers use cryptographic signatures to ensure only authorized addresses can execute
   your workflow. During **local simulation**, you can use empty authorization configs to simplify testing—just remember
-  to add `authorizedKeys` before deploying.
+  to add `authorizedKeys` before deploying. Learn more: [Configuration &
+  Handler](/cre/guides/workflow/using-triggers/http-trigger/configuration-go#configuration-and-handler).
 </Aside>
 
 ## When to use HTTP triggers

src/content/cre/guides/workflow/using-triggers/http-trigger/overview-ts.mdx

@@ -24,10 +24,11 @@ When you deploy a workflow with an HTTP trigger:
 1. **CRE validates the signature** against your configured `authorizedKeys`
 1. **If authorized**, your workflow callback executes with the request payload
 
-<Aside type="note" title="Security by design">
+<Aside type="caution" title="Authorization required for deployed workflows">
   For **deployed workflows**, HTTP triggers use cryptographic signatures to ensure only authorized addresses can execute
   your workflow. During **local simulation**, you can use empty authorization configs to simplify testing—just remember
-  to add `authorizedKeys` before deploying.
+  to add `authorizedKeys` before deploying. Learn more: [Configuration &
+  Handler](/cre/guides/workflow/using-triggers/http-trigger/configuration-ts#configuration-and-handler).
 </Aside>
 
 ## When to use HTTP triggers

src/content/cre/llms-full-go.txt

@@ -12071,7 +12071,7 @@ func InitWorkflow(config *Config, logger *slog.Logger, secretsProvider cre.Secre
     authorizedKeys := []*http.AuthorizedKey{
         {
             Type:      http.KeyType_KEY_TYPE_ECDSA_EVM,
-            PublicKey: config.HTTPPublicKey,
+            PublicKey: config.AuthorizedEVMAddress,
         },
     }
 
@@ -12143,10 +12143,11 @@ When you deploy a workflow with an HTTP trigger:
 4. **CRE validates the signature** against your configured `authorizedKeys`
 5. **If authorized**, your workflow callback executes with the request payload
 
-<Aside type="note" title="Security by design">
+<Aside type="caution" title="Authorization required for deployed workflows">
   For **deployed workflows**, HTTP triggers use cryptographic signatures to ensure only authorized addresses can execute
   your workflow. During **local simulation**, you can use empty authorization configs to simplify testing—just remember
-  to add `authorizedKeys` before deploying.
+  to add `authorizedKeys` before deploying. Learn more: [Configuration &
+  Handler](/cre/guides/workflow/using-triggers/http-trigger/configuration-go#configuration-and-handler).
 </Aside>
 
 ## When to use HTTP triggers

src/content/cre/llms-full-ts.txt

@@ -10966,7 +10966,7 @@ You create an HTTP trigger by calling the `HTTPCapability.trigger()` method. Its
 import { cre, type Runtime, type HTTPPayload, Runner } from "@chainlink/cre-sdk"
 
 type Config = {
-  httpPublicKey: string
+  authorizedEVMAddress: string
 }
 
 // Callback function that runs when an HTTP request is received
@@ -10985,7 +10985,7 @@ const initWorkflow = (config: Config) => {
         authorizedKeys: [
           {
             type: "KEY_TYPE_ECDSA_EVM",
-            publicKey: config.httpPublicKey,
+            publicKey: config.authorizedEVMAddress,
           },
         ],
       }),
@@ -11059,10 +11059,11 @@ When you deploy a workflow with an HTTP trigger:
 4. **CRE validates the signature** against your configured `authorizedKeys`
 5. **If authorized**, your workflow callback executes with the request payload
 
-<Aside type="note" title="Security by design">
+<Aside type="caution" title="Authorization required for deployed workflows">
   For **deployed workflows**, HTTP triggers use cryptographic signatures to ensure only authorized addresses can execute
   your workflow. During **local simulation**, you can use empty authorization configs to simplify testing—just remember
-  to add `authorizedKeys` before deploying.
+  to add `authorizedKeys` before deploying. Learn more: [Configuration &
+  Handler](/cre/guides/workflow/using-triggers/http-trigger/configuration-ts#configuration-and-handler).
 </Aside>
 
 ## When to use HTTP triggers