[PM-41330] feat: Add custom header support for self-hosted environments - #7226
Open
jalenfran wants to merge 1 commit into
Open
[PM-41330] feat: Add custom header support for self-hosted environments#7226jalenfran wants to merge 1 commit into
jalenfran wants to merge 1 commit into
Conversation
Allow configuring custom HTTP headers on the pre-auth self-hosted environment screen, applied to every request sent to the environment's hosts. Supports reverse proxies that gate access on a header, such as Cloudflare Access. - Store header values in encrypted SharedPreferences; only an opaque identifier is persisted in EnvironmentUrlDataJson, mirroring keyUri - Inject headers via a network-level OkHttp interceptor scoped to the environment's hosts, so credentials never reach third parties and never appear in the application-level debug HTTP logs - Apply headers to Glide icon requests, which bypass the Retrofit pipeline - Reference-count cleanup across accounts on logout and account deletion, and when replacing the pre-auth environment with a built-in region - Redact Cookie and Set-Cookie values from the debug HTTP logs
Collaborator
|
Thank you for your contribution! We've added this to our internal tracking system for review. Details on our contribution process can be found here: https://contributing.bitwarden.com/contributing/pull-requests/community-pr-process. |
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
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.
🎟️ Tracking
Community feature request: Allow custom header for the Bitwarden mobile app (Android/iOS)
📔 Objective
Allow configuring custom HTTP headers on the pre-auth self-hosted environment screen, applied to
every request sent to the environment's hosts. This lets the app reach self-hosted servers behind
reverse proxies that gate access on a header — e.g. Cloudflare Access service tokens
(
CF-Access-Client-Id/CF-Access-Client-Secret) — which currently block the mobile app eventhough the web vault works via browser-based authentication.
EnvironmentUrlDataJson, mirroringkeyUrihost match), so credentials never reach third parties and never appear in the application-level
debug HTTP logs
environment is replaced (built-in region selection, MDM-managed URLs)
CookieandSet-Cookievalues from the debug HTTP logs📸 Screenshots