Custom Proxy / PAC support to Proxy website (Edge) (WebView2)

I open this Feature request on the behave on a Customer:

Please add Custom Proxy / PAC support to Proxy website (Edge) (WebView2) so that WebView2 network traffic can be routed through a proxy configured in RDM, instead of being limited to System Proxy or No Proxy.
Context / Use case
I’m posting this on behalf of an enterprise customer with a restricted network:

• Windows servers/workstations do not have direct Internet access
• Outbound web access is allowed only via a controlled proxy (often with inspection / allowlists)
• Setting a system-wide proxy is problematic (can impact other apps/admin workflows), and PAC per host is not always manageable at scale

This becomes a blocker when RDM uses WebView2 (Edge) for authentication flows (e.g., Okta used with a Delinea integration), because WebView2 traffic cannot be forced through an RDM-defined proxy today.
Current behavior

• In RDM, Proxy website (Edge) only offers:
  • Use System Proxy
  • No Proxy
• The existing RDM “Custom Proxy” settings apply only to certain internal features (e.g., some website-related/internal requests), but do not apply to WebView2 (Edge).
• Result: If the environment requires a proxy to reach Okta/Delinea endpoints, the authentication/web flow fails unless Windows System Proxy is configured.

Expected behavior
Add a third mode (or equivalent) for Proxy website (Edge):

• Custom Proxy (host/port + optional auth) and/or
• PAC URL support
• Optional bypass/exceptions list (domains/IP ranges) so only required destinations go through the proxy

Ideally this could be configured:

• Globally (RDM application settings) and/or
• Per data source / integration (e.g., Delinea datasource) and/or
• Per entry / vault (advanced)

Why it matters (impact)
This limitation blocks upgrades/adoption in locked-down enterprise environments where:

• Okta is mandatory for SSO
• Web traffic must traverse a proxy
• System-wide proxy changes are undesirable or not feasible

Workarounds tried

• Configure Windows System Proxy (or PAC with exceptions) and set RDM WebView2 to Use System Proxy
• This can work, but it’s often not acceptable operationally (global impact, complexity, exceptions management).

Versions (example from the affected environment)

• RDM: 2025.2.x
• Devolutions Server: 2025.2.x
• (Exact versions available if needed.)

Thanks!