You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/docs/cloudflare-one/policies/gateway/http-policies/tenant-control.mdx
+17-6Lines changed: 17 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,10 +9,6 @@ With Gateway tenant control, you can allow your users access to corporate SaaS a
9
9
10
10
When creating an HTTP policy with an Allow action, you will have the option to configure custom headers. Gateway can use custom headers to control SaaS application access. If a user's HTTP request is headed to your organization's account for the SaaS application, Gateway will approve the request. If the request does not match the information in the header, Gateway will block the request.
11
11
12
-
## Note
13
-
14
-
Customer headers will not appear in a HAR file taken from your browser. This is due to the header being injected by Gateway after the request leaves your browser. To verify if a custom header is being applied, temporarily add a selector for *Domain > In > httpbin.org* to your Gateway rule, once saved go to [`httpbin.org/anything`](https://httpbin.org/anything) and verify the custom header is shown.
15
-
16
12
## Add custom headers for a SaaS application
17
13
18
14
To create an HTTP policy with custom headers:
@@ -27,6 +23,22 @@ To create an HTTP policy with custom headers:
27
23
28
24
Your policy is now displayed in your list of HTTP policies. When your users attempt to authenticate your configured SaaS application with a personal account, authentication will fail.
29
25
26
+
### Verify custom headers
27
+
28
+
If you save a HAR (HTTP Archive) file from a browser to analyze your web traffic, custom headers defined with Gateway will not appear in the file. This is because Gateway injects the header after the request leaves the browser.
29
+
30
+
To verify Gateway is applying a custom header:
31
+
32
+
1. In your policy with custom headers, add a selector to match traffic for [HTTPBin](https://httpbin.org/), an open-source site for testing HTTP requests. For example:
| Application | in |_Google Workspace_| And | Allow | Block |
37
+
| Domain | in |`httpbin.org`||||
38
+
39
+
2. On your device, go to [`httpbin.org/anything`](https://httpbin.org/anything). Your custom header will appear in the list of headers.
40
+
3. (Optional) Remove the HTTPBin expression from your policy.
41
+
30
42
## Common policy configurations
31
43
32
44
Depending on which SaaS application your organization needs access to, different tenant control policies are required.
@@ -121,7 +133,7 @@ You can include custom headers in an HTTP policy to allow your users through [Cl
121
133
122
134
You can configure [Browser Isolation](/cloudflare-one/policies/browser-isolation/) to send custom headers. This is useful for implementing tenant control for isolated SaaS applications or sending arbitrary custom request headers to isolated websites.
123
135
124
-
To use custom headers with Browser Isolation, create two HTTP policies targeting the same domain or application group. For example, you can create policies for [httpbin](https://httpbin.org/), an open-source site for testing HTTP requests:
136
+
To use custom headers with Browser Isolation, create two HTTP policies targeting the same domain or application group. For example, you can create policies for [HTTPBin](https://httpbin.org/), an open-source site for testing HTTP requests:
125
137
126
138
1. Create an Isolate policy for `httpbin.org`.
127
139
@@ -140,4 +152,3 @@ To use custom headers with Browser Isolation, create two HTTP policies targeting
140
152
|`Example-Header`|`example-value`|
141
153
142
154
3. Go to [`httpbin.org/anything`](https://httpbin.org/anything). Cloudflare will render the site in an isolated browser. Your custom header will appear in the list of headers.
0 commit comments