[Cloudflare One] Document TLS inspection requirement for authorization proxy endpoints#31125
Open
grstnhbr wants to merge 2 commits into
Open
[Cloudflare One] Document TLS inspection requirement for authorization proxy endpoints#31125grstnhbr wants to merge 2 commits into
grstnhbr wants to merge 2 commits into
Conversation
…n proxy endpoints Authorization proxy endpoints always perform TLS decryption to read the auth cookie, regardless of account-level TLS settings. Add this as a documented limitation and clarify the certificate install step.
Review💡 3 suggestions found in commit Suggestions (3)
CommandsOnly codeowners can run commands. Post a comment with the command to trigger it.
|
Contributor
Author
|
/bonk review this PR |
Contributor
|
/bonk review |
| ### 3a. Install Cloudflare certificate | ||
|
|
||
| To use Gateway HTTP policies with proxy endpoints, you must [install a Cloudflare certificate](/cloudflare-one/team-and-resources/devices/user-side-certificates/) on your devices. This allows Gateway to inspect HTTPS traffic and apply policies such as blocking specific domains or displaying the Gateway block page. | ||
| You must [install a Cloudflare certificate](/cloudflare-one/team-and-resources/devices/user-side-certificates/) on your devices. For [authorization endpoints](#authorization-endpoint), Gateway always performs TLS inspection to read the authorization cookie, so the certificate is required for the endpoint to function. For [source IP endpoints](#source-ip-endpoint), the certificate is required to apply Gateway HTTP policies such as blocking specific domains or displaying the Gateway block page. |
Contributor
There was a problem hiding this comment.
Use active voice instead of passive ('is required'):
Suggested change
| You must [install a Cloudflare certificate](/cloudflare-one/team-and-resources/devices/user-side-certificates/) on your devices. For [authorization endpoints](#authorization-endpoint), Gateway always performs TLS inspection to read the authorization cookie, so the certificate is required for the endpoint to function. For [source IP endpoints](#source-ip-endpoint), the certificate is required to apply Gateway HTTP policies such as blocking specific domains or displaying the Gateway block page. | |
| You must [install a Cloudflare certificate](/cloudflare-one/team-and-resources/devices/user-side-certificates/) on your devices. For [authorization endpoints](#authorization-endpoint), Gateway always performs TLS inspection to read the authorization cookie, so the endpoint will not function without the certificate. For [source IP endpoints](#source-ip-endpoint), you must install the certificate to apply Gateway HTTP policies such as blocking specific domains or displaying the Gateway block page. |
Contributor
|
Review submitted for PR #31125. Verdict: 1 inline suggestion posted. The new content is technically accurate; the only remaining issue is minor passive voice on line 317. Issue flagged:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Context: a customer discovered during testing that TLS decryption happens by default on authorization proxy endpoints despite being disabled at the account level. This is expected behavior - the auth cookie can only be read from decrypted requests - but it was not documented.