Browser Extension
BusinessProxy uses a browser extension to request a short-lived proxy session, apply the workspace routing policy, and answer proxy-auth challenges automatically. Users never type reusable session credentials. Install the extension, set or receive the API URL, sign in, and connect.
Install the BusinessProxy browser extension for Chrome/Chromium, Firefox, Opera or an Edge-compatible environment, open Options and set the API URL unless it is pushed by policy, sign in from the popup, then click Connect. The extension registers the device key if needed and requests short-lived proxy credentials.
The proxy session is device-bound and short-lived. Sensitive session endpoints are signed with a device ID, timestamp and ECDSA P-256 signature. The session response returns a proxy node, routing policy and random credentials with their own expiry.
Account login and proxy access use different secrets. The extension receives random proxy credentials for the current session only. BusinessProxy validates those credentials server-side with a keyed one-way digest; the raw proxy secret is not stored.
Permissions
| Permission | Purpose |
|---|---|
proxy | Configure browser proxy settings while BusinessProxy is connected. |
storage | Store minimal extension state and read managed browser settings. |
alarms | Run heartbeat, expiry and cleanup checks for the proxy session. |
notifications | Notify the user when an administrator ends a proxy session or signs the browser out. |
cookies | Remove the BusinessProxy private-app session cookie when the user turns proxy off. |
downloads | Cancel or erase downloads when a protected session policy requires download deterrence. |
declarativeNetRequest | Attach a browser-bound private-app header only to the published app alias. |
webNavigation | Open configured private-app browser hosts through the managed alias. |
webRequest | Receive proxy-authentication challenge events for routed browser requests. |
webRequestAuthProvider | Respond to proxy-auth challenges with short-lived session credentials. |
content_scripts: content-protection.js | Apply configured content-protection controls such as watermarking, copy/print controls, screenshot deterrence and private-app page controls. |
host_permissions: <all_urls> | Allows the browser to deliver proxy-auth challenges for requests routed through the configured proxy, regardless of destination site. |
FAQ
Yes. Users need the BusinessProxy browser extension for a supported desktop browser. The point is that there is no OS-level agent and no device-wide VPN client. Enforced deployments require customer-managed browser or device policy validation.
Browsers require broad host access so the extension can receive proxy-authentication challenges for routed requests and run the declared content-protection script where a protected session requires it. The extension does not use a tabs permission or arbitrary page scripting permission.
No. Account login and proxy access use different credentials. Session credentials are random and short-lived. BusinessProxy validates them with a server-side keyed one-way digest and does not store the raw session credential or reuse the account password.