Closed Bug 2034102 Opened 4 months ago Closed 2 months ago

Expose proxy protection state as a reusable API

Categories

(Firefox :: IP Protection, enhancement)

enhancement

Tracking

()

RESOLVED FIXED
154 Branch
Tracking Status
firefox154 --- fixed

People

(Reporter: jporter, Assigned: sstreich)

References

Details

(Whiteboard: [fx-vpn])

Attachments

(1 file)

For Firefox Enterprise, we are implementing a custom UX for the Access Connector feature that utilizes the IPProtection plumbing. The IPProtectionToolbarButton contains logic to determine whether a given principal is being proxied through IPPProtection. We need to be able to mirror this behavior in other contexts without reimplementing or duplicating the logic.

I spoke with @basti about exposing as a reusable method on IPProxyManager so that consumers can query the proxy protection state for a given principal without depending on the toolbar button's internal implementation. This should include handling error states (e.g., VPN unavailable, network disconnected, connection errors) to ensure consumers can respond appropriately across all possible proxy states.

Whiteboard: [fx-vpn]
Assignee: nobody → sstreich
Status: NEW → ASSIGNED
Pushed by sstreich@mozilla.com: https://github.com/mozilla-firefox/firefox/commit/da6613bf06aa https://hg.mozilla.org/integration/autoland/rev/e1c5fb871c77 Expose a shared API to report Exclusion/Inclusion rules for a Principal r=joporter,ip-protection-reviewers,kpatenio
Status: ASSIGNED → RESOLVED
Closed: 2 months ago
Resolution: --- → FIXED
Target Milestone: --- → 154 Branch
QA Whiteboard: [qa-triage-done-c155/b154]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: