Skip Navigation

Search

How to run the .NET Console in Chromium-based browsers for agents under GPO
Answer ID 11587   |   Last Review Date 11/02/2020

Can't download .Net Console in latest Microsoft Edge Version

Environment:

Oracle B2C Service versions 19C and newer. *

Resolution:

For IT staff under GPO, changes will need to be made to the default browser settings in Microsoft Edge or Google Chrome to allow Oracle B2C Service to install and update. 

Click the plus sign next to the appropriate heading below to expand that section for viewing.

Part 1: Configuring Microsoft Edge (Native Support)

Step 1: Enable the ClickOnce Protocol

You need to flip the master switch to allow Edge to process ClickOnce links.

GPO Path: Computer Configuration or User Configuration -> Administrative Templates -> Microsoft Edge

Policy Name: Allow users to open files using the ClickOnce protocol

Setting: Set to Enabled

Registry alternative: [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge] -> Create a DWORD named ClickOnceEnabled and set it to 1.

 

Step 2: Suppress the "Open/Save" File Prompts (Crucial for a seamless experience)

Even if ClickOnce is allowed, Edge will still prompt the user to "Keep" or "Open" the download every time. To auto-launch your specific app, whitelist its hosting domain:

GPO Path: ... -> Administrative Templates -> Microsoft Edge

Policy Name: List of file types that should be automatically opened on download

Setting: Set to Enabled, click Show, and add this exact string:

{"file_extension": "application", "domains": ["your-internal-domain.com"]}

Part 2: Configuring Google Chrome (Requires Extension)

Step 1: Force-Install a ClickOnce Extension

You must push a verified ClickOnce helper extension to your Chrome users. A trusted standard is the Meta4 ClickOnce Launcher or similar enterprise tools.

GPO Path: Computer Configuration or User Configuration -> Administrative Templates -> Google -> Google Chrome -> Extensions

Policy Name: Configure the list of force-installed apps and extensions

Setting: Set to Enabled, click Show, and add the extension ID appended with the update URL.

 

Step 2: Whitelist the App Domain in Chrome

To prevent Chrome from blocking the extension's communication with your website:

GPO Path: ... -> Administrative Templates -> Google Chrome

Policy Name: Allow lists of URLs to open external protocols without a prompt

Setting: Set to Enabled, click Show, and input the format scheme to trust your specific domain:

[{"protocol": "clickonce", "allowed_origins": ["https://your-internal-domain.com"]}]