[GH-ISSUE #1302] Custom HTTP Header for Cloudflare Access #809

New issue

Open

opened 2026-03-02 02:19:11 +03:00 by kerem · 0 comments

kerem commented

2026-03-02 02:19:11 +03:00

Owner

Originally created by @luminous706 on GitHub (Oct 3, 2022).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1302

Hello, for multi-tenancy, Tactical RMM requires a server in the cloud with port 443 opened to the internet, especially if deployed at scale.

By putting the domains behind Cloudflare Access (Zero Trust) (api, rmm, etc), only the tactical agents with the special HTTP header token would be able to pass through the Cloudflare proxy, adding a lot of protections to Tactical.

Could you look into implementing such feature? I think just a way to add a custom web header every time Tactical reaches out to the server could work.

Originally created by @luminous706 on GitHub (Oct 3, 2022). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1302 Hello, for multi-tenancy, Tactical RMM requires a server in the cloud with port 443 opened to the internet, especially if deployed at scale. By putting the domains behind Cloudflare Access (Zero Trust) (api, rmm, etc), only the tactical agents with the special HTTP header token would be able to pass through the Cloudflare proxy, adding a lot of protections to Tactical. ![image](https://user-images.githubusercontent.com/71604658/193694161-cd16449d-41e5-4cae-a0cc-097d4c579d3a.png) Could you look into implementing such feature? I think just a way to add a custom web header every time Tactical reaches out to the server could work.