Add Cloudflare Zero Trust service token support#12
Open
romainfrayssinet wants to merge 2 commits intonewmaterialco:mainfrom
Open
Add Cloudflare Zero Trust service token support#12romainfrayssinet wants to merge 2 commits intonewmaterialco:mainfrom
romainfrayssinet wants to merge 2 commits intonewmaterialco:mainfrom
Conversation
Injects CF-Access-Client-ID and CF-Access-Client-Secret headers at WebSocket upgrade time when configured. Credentials stored in Keychain. Settings UI includes a toggle to enable/disable with animated fields.
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
1 participant
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
CF-Access-Client-IDandCF-Access-Client-SecretHTTP headers to the WebSocket upgrade request when Cloudflare Zero Trust credentials are configuredHow it works
Cloudflare Access requires service token headers to be present in the initial HTTP upgrade request — they cannot be sent after the WebSocket connection is established. Switching from
webSocketTask(with: URL)towebSocketTask(with: URLRequest)allows injecting these headers at the right moment.The feature is fully opt-in: leaving the toggle off keeps the existing behaviour unchanged.