2040381 - User should be aware of an access connector failure

Status: REOPENED

(Enterprise Products :: Firefox, enhancement, P1)

Comment 1

[Romain Testard [:RT]]

Matt, can you please help here with input on how best we should handle an error to connect on the access connector side. The web page won't load in that case and we need a UI affordance to let the user know that the access connector is down (error page, variation of the access connector toolbar button, ...)

Comment 2

[Enterprise UX]

Attachment: AC-down.png

The proposed solution has two parts: a full-page error message and a URL bar doorhanger.
When the Access Connector is unavailable, users should see a standard full-page error using the grey Access Connector icon to keep the state calm, making it clear the user has not tried to access a domain they shouldn't. The message reads:
"Your organization routes this website through a secure connection service, but that service is currently unavailable."
And advises the user to contact their administrator if they need access.

In the URL bar, a new Access Connector slash icon should indicate the unavailable state; when clicked, it opens a doorhanger titled “Access Connector unavailable” explaining that "the site is configured to use additional authentication methods and routes for a secure enterprise proxy, but the Access Connector is currently unavailable", with guidance to try again later or contact an administrator if the issue continues.

Figma files: https://www.figma.com/design/xYH6L8QrDz0Q16XFvdo7We/%F0%9F%A6%8A-Client-Design?node-id=2541-8998&t=XrYQhMzAjmeTbDeU-1

Comment 3

[Romain Testard [:RT]]

Thanks Matt, this looks all right to me, updating the acceptance criteria accordingly

Comment 4

[Josh Porter [:jporter]]

Just dropping a note here since I've been taking a look at some of the error paths in the IPProtection/VPN wrt bug 2035186, which is specific to a failure to obtain an auth token.

In the process of digging through the code I came across bug 2012592 which modifies the netError handling to show a custom message when the VPN is active and there is a proxyConnectFailure, which is likely the same scenario we want to handle here (plus the button icon/panel text once that's landed).

Comment 5

[BMO Github Automation]

Attachment: [mozilla/enterprise-firefox] Bug 2040381 - Show custom error page when Access Connector is unavailable (#1033)

Comment 6

[BMO Github Automation]

Attachment: [mozilla/enterprise-firefox] Bug 2040381 - Show error state in Access Connector urlbar button and panel when proxy is unavailable (#1048)

Comment 7

[BMO Github Automation]

Authored by https://github.com/jporter-dev
https://github.com/mozilla/enterprise-firefox/commit/7adba2769270e9efb37503f458e5f4b49bb5b55f
[enterprise-main] Bug 2040381 - Show custom error page when Access Connector is unavailable (#1033)

Comment 8

[Josh Porter [:jporter]]

The initial proxy neterror page is merged. The Access Connector button error state PR is created but depends on bug 2026242 to land.

Comment 9

[Josh Porter [:jporter]]

Part 1 of this has landed (proxy neterror page). Now that Access Connector UX has landed, part 2 to reflect the error status in the urlbar button is almost ready to land: https://github.com/mozilla/enterprise-firefox/pull/1048

Comment 10

[Josh Porter [:jporter]]

Attachment: access-connector-error-critical.png

A good point was raised by Janika that the proposed Access Connector error icon should use the critical or warn color to represent the error instead of the information used by the "active" state.

I've included an example of the Access Connector error state using the critical color, and have it shown alongside the Lockdown Mode icon that uses the information color just for reference.

Let me know which color you prefer for this state, thank you!

Comment 11

[Enterprise UX]

Excellent, a great suggestion. As it's a blocking action I actually think Critical makes sense here. Thank you!

Comment 12

[BMO Github Automation]

Attachment: [mozilla/enterprise-firefox] Bug 2040381 - Register security event for Access Connector connection error (#1121)