Add signed header support to HTTP proxy integration

[josharian]

Author: philz42
Channel: #feedback
Link: https://discord.com/channels/1405685085923049482/1405686161791516873/1550599323379699854

---

Request

Add support for signed/authenticated headers in the HTTP proxy integration for non-exe.dev endpoints.

Context

User is deploying the HTTP proxy integration across a fleet of ~50 VMs, where each VM has a unique API key to their service. They discovered that VMs pass along information about themselves in headers, but these headers are not being passed along to their external API endpoints (non-exe.dev).

The user requested the ability to use signed versions of these headers with the regular HTTP proxy integration to authenticate requests to their own API.

Discussion

• Single integration with VM identification headers is viable as an alternative to one integration per VM
• Current limitation: headers containing VM info don't get passed to external endpoints
• Requested feature: signed/authenticated headers for HTTP proxy integration
• This has been added to the roadmap as a potential enhancement

[josharian]

🔍 Potential duplicates found:

• Add VM-to-VM HTTP request authentication with VM identity headers #181: Both issues request the same feature: adding authentication/signing support to HTTP proxy headers for VM-to-VM communication. Issue Add VM-to-VM HTTP request authentication with VM identity headers #181 specifically mentions 'VM-to-VM HTTP request authentication with VM identity headers' which is the core feature requested in Add signed header support to HTTP proxy integration #234 for authenticated headers in HTTP proxy integration.

This is an automated check. Please review and close as duplicate if appropriate.