diff --git a/.editorconfig b/.editorconfig index dad6b582..9203ffd5 100644 --- a/.editorconfig +++ b/.editorconfig @@ -4,7 +4,7 @@ root = true [*] indent_style = space -indent_size = 2 +indent_size = 4 end_of_line = lf charset = utf-8 trim_trailing_whitespace = true diff --git a/content/en/docs/software_and_hardware/browser_extensions/weblogin/_index.md b/content/en/docs/software_and_hardware/browser_extensions/weblogin/_index.md new file mode 100644 index 00000000..0f510bc5 --- /dev/null +++ b/content/en/docs/software_and_hardware/browser_extensions/weblogin/_index.md @@ -0,0 +1,11 @@ +--- +title: "WebLogin" +description: "" +lead: "" +date: 2023-09-11T11:37:06+03:30 +lastmod: 2023-09-11T11:37:06+03:30 +draft: false +images: [] +type: docs +weight: 322000 +--- diff --git a/content/en/docs/software_and_hardware/browser_extensions/weblogin/configure_weblogin_on_chrome_for_windows_with_intune.md b/content/en/docs/software_and_hardware/browser_extensions/weblogin/configure_weblogin_on_chrome_for_windows_with_intune.md new file mode 100644 index 00000000..f627fa52 --- /dev/null +++ b/content/en/docs/software_and_hardware/browser_extensions/weblogin/configure_weblogin_on_chrome_for_windows_with_intune.md @@ -0,0 +1,107 @@ +--- +title: "Configure on Chrome for Windows using Intune" +description: "" +lead: "" +date: 2025-12-30T14:40:56+01:00 +lastmod: 2025-12-30T14:40:56+01:00 +draft: false +images: [ ] +menu: + docs: + parent: "weblogin" +type: docs +weight: 326000 +toc: true +--- + +This guide provides a PowerShell script for IT Administrators to configure the WebLogin extension on Google Chrome via +Microsoft Intune. This script manages complex configuration objects—including nested server addresses, automation +workflows, and operational options—by writing directly to the Windows Registry. + +## Prerequisites + +- Intune Administrator permissions. + +- Windows 10/11 devices enrolled in Intune. + +- The WebLogin extension must be + force-installed ([Guide](/docs/software_and_hardware/browser_extensions/weblogin/install_weblogin_on_chrome_for_windows_with_intune/)). + +## Step 1: Create the PowerShell Script + +Create a script named `Configure-WebLogin-Chrome.ps1`. Update the variables in the script to match your organization's +environment. Please note all the configs are optional and you should only declare the needed configs. + +```shell +# Declare needed configs + +$api_key = "your-api-key-goes-here" +$workspace_id = "your-workspace-id-goes-here" +$server_address = "{ `"env`": `"onpremise`", `"env`": `"https://domain.com/api/url`" }" +$options = "{ `"handlePasskeyRequests`": { `"value`": true }, `"allowAddingNewPasswords`": { `"value`": true }, `"allowPasswordUpdatePrompts`": { `"value`": true }, `"useEmbeddedNumpad`": { `"value`": true }, `"keystroking`": { `"value`": true }, `"debugMode`": { `"value`": true }, `"autofillPrompt`": { `"value`": true, `"includedUrls`": [`"https://domain.com/login`"], `"excludedUrls`": [`"https://domain.com/login`"] } }" +$workflow_automation = "{ `"action`": `"login`", `"window`": `"incognito`", `"hint`": { `"type`": `"pinTapPage`" }, `"urls`": [ { `"method`": `"passkey`", `"url`": `"https://myapps.microsoft.com`" } ] }" + +$registry_path = "HKLM:\SOFTWARE\Policies\Google\Chrome\3rdparty\extensions\eagmgpbjpedchliifpgfgogdknnmkaej\policy" + +$parent_path = Split-Path -Path $registry_path + +# Create policy path for the WebLogin if it does not exist + +if (!(Test-Path $parent_path)) { + New-Item -Path $parent_path -Force -ItemType Directory | Out-Null +} + +if (!(Test-Path $parent_path\policy)) { + New-Item -Path ("$parent_path\policy") -Force -ItemType Directory | Out-Null +} + +# Set values + +Set-ItemProperty -Path $registry_path -Name "apiKey" -Value $api_key +Set-ItemProperty -Path $registry_path -Name "workspaceID" -Value $workspace_id +Set-ItemProperty -Path $registry_path -Name "serverAddress" -Value $server_address -Type ExpandString +Set-ItemProperty -Path $registry_path -Name "options" -Value $options -Type ExpandString +Set-ItemProperty -Path $registry_path -Name "workflowAutomation" -Value $workflow_automation -Type ExpandString + +exit 0 +``` + +## Step 2: Deployment via Intune + +1. Sign in to the [Microsoft Intune admin center](https://intune.microsoft.com/). + +2. Navigate to **Devices > Scripts and remediations > Platform scripts**. + +3. Click **Add**. + + ![alt](/images/vendor/weblogin/create_script.jpg) + +4. **Basics:** Name the script (e.g., Chrome - WebLogin Extension Managed Config). + +5. **Script Settings**: + + - **Script location:** Upload `Configure-WebLogin-Chrome.ps1`. + + - **Run this script using the logged on credentials:** No. + + - **Enforce script signature check:** No. + + - **Run script in 64-bit PowerShell Host:** No. + + ![alt](/images/vendor/weblogin/script_settings_chrome.jpg) + +6. **Assignments:** Assign to the device group that has the WebLogin extension force-installed. + +## Step 3: Verification + +To confirm the settings have been applied correctly: + +1. **Check the Registry:** Open `regedit` and navigate to: + `HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\3rdparty\extensions\eagmgpbjpedchliifpgfgogdknnmkaej\policy` + Verify that all declared keys (`apiKey`, `serverAddress`, etc.) are present. + +2. **Verify in Chrome:** Open Chrome and navigate to `chrome://policy`. Find the entry for + `eagmgpbjpedchliifpgfgogdknnmkaej`. Under Policy Value, click Show More to see the structured JSON data being + consumed by the extension. + +> Intune can take up to 24 hours to run your configuration script on the end device. diff --git a/content/en/docs/software_and_hardware/browser_extensions/weblogin/configure_weblogin_on_edge_for_windows_with_intune.md b/content/en/docs/software_and_hardware/browser_extensions/weblogin/configure_weblogin_on_edge_for_windows_with_intune.md new file mode 100644 index 00000000..5f272b0c --- /dev/null +++ b/content/en/docs/software_and_hardware/browser_extensions/weblogin/configure_weblogin_on_edge_for_windows_with_intune.md @@ -0,0 +1,107 @@ +--- +title: "Configure on Edge for Windows using Intune" +description: "" +lead: "" +date: 2025-12-30T14:40:56+01:00 +lastmod: 2025-12-30T14:40:56+01:00 +draft: false +images: [ ] +menu: + docs: + parent: "weblogin" +type: docs +weight: 325000 +toc: true +--- + +This guide provides a PowerShell script for IT Administrators to configure the WebLogin extension on Microsoft Edge via +Microsoft Intune. This script manages complex configuration objects—including nested server addresses, automation +workflows, and operational options—by writing directly to the Windows Registry. + +## Prerequisites + +- Intune Administrator permissions. + +- Windows 10/11 devices enrolled in Intune. + +- The WebLogin extension must be + force-installed ([Guide](/docs/software_and_hardware/browser_extensions/weblogin/install_weblogin_on_edge_for_windows_with_intune/)). + +## Step 1: Create the PowerShell Script + +Create a script named `Configure-WebLogin-Edge.ps1`. Update the variables in the script to match your organization's +environment. Please note all the configs are optional and you should only declare the needed configs. + +```shell +# Declare needed configs + +$api_key = "your-api-key-goes-here" +$workspace_id = "your-workspace-id-goes-here" +$server_address = "{ `"env`": `"onpremise`", `"env`": `"https://domain.com/api/url`" }" +$options = "{ `"handlePasskeyRequests`": { `"value`": true }, `"allowAddingNewPasswords`": { `"value`": true }, `"allowPasswordUpdatePrompts`": { `"value`": true }, `"useEmbeddedNumpad`": { `"value`": true }, `"keystroking`": { `"value`": true }, `"debugMode`": { `"value`": true }, `"autofillPrompt`": { `"value`": true, `"includedUrls`": [`"https://domain.com/login`"], `"excludedUrls`": [`"https://domain.com/login`"] } }" +$workflow_automation = "{ `"action`": `"login`", `"window`": `"incognito`", `"hint`": { `"type`": `"pinTapPage`" }, `"urls`": [ { `"method`": `"passkey`", `"url`": `"https://myapps.microsoft.com`" } ] }" + +$registry_path = "HKLM:\SOFTWARE\Policies\Microsoft\Edge\3rdparty\extensions\eagmgpbjpedchliifpgfgogdknnmkaej\policy" + +$parent_path = Split-Path -Path $registry_path + +# Create policy path for the WebLogin if it does not exist + +if (!(Test-Path $parent_path)) { + New-Item -Path $parent_path -Force -ItemType Directory | Out-Null +} + +if (!(Test-Path $parent_path\policy)) { + New-Item -Path ("$parent_path\policy") -Force -ItemType Directory | Out-Null +} + +# Set values + +Set-ItemProperty -Path $registry_path -Name "apiKey" -Value $api_key +Set-ItemProperty -Path $registry_path -Name "workspaceID" -Value $workspace_id +Set-ItemProperty -Path $registry_path -Name "serverAddress" -Value $server_address -Type ExpandString +Set-ItemProperty -Path $registry_path -Name "options" -Value $options -Type ExpandString +Set-ItemProperty -Path $registry_path -Name "workflowAutomation" -Value $workflow_automation -Type ExpandString + +exit 0 +``` + +## Step 2: Deployment via Intune + +1. Sign in to the [Microsoft Intune admin center](https://intune.microsoft.com/). + +2. Navigate to **Devices > Scripts and remediations > Platform scripts**. + +3. Click **Add**. + + ![alt](/images/vendor/weblogin/create_script.jpg) + +4. **Basics:** Name the script (e.g., Edge - WebLogin Extension Managed Config). + +5. **Script Settings**: + + - **Script location:** Upload `Configure-WebLogin-Edge.ps1`. + + - **Run this script using the logged on credentials:** No. + + - **Enforce script signature check:** No. + + - **Run script in 64-bit PowerShell Host:** No. + + ![alt](/images/vendor/weblogin/script_settings_edge.jpg) + +6. **Assignments:** Assign to the device group that has the WebLogin extension force-installed. + +## Step 3: Verification + +To confirm the settings have been applied correctly: + +1. **Check the Registry:** Open `regedit` and navigate to: + `HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\3rdparty\extensions\eagmgpbjpedchliifpgfgogdknnmkaej\policy` + Verify that all declared keys (`apiKey`, `serverAddress`, etc.) are present. + +2. **Verify in Edge:** Open Edge and navigate to `edge://policy`. Find the entry for + `eagmgpbjpedchliifpgfgogdknnmkaej`. Under Policy Value, click Show More to see the structured JSON data being + consumed by the extension. + +> Intune can take up to 24 hours to run your configuration script on the end device. diff --git a/content/en/docs/software_and_hardware/browser_extensions/weblogin/install_weblogin_on_chrome_for_windows_with_intune.md b/content/en/docs/software_and_hardware/browser_extensions/weblogin/install_weblogin_on_chrome_for_windows_with_intune.md new file mode 100644 index 00000000..c471c192 --- /dev/null +++ b/content/en/docs/software_and_hardware/browser_extensions/weblogin/install_weblogin_on_chrome_for_windows_with_intune.md @@ -0,0 +1,102 @@ +--- +title: "Install on Chrome for Windows using Intune" +description: "" +lead: "" +date: 2025-12-30T14:40:56+01:00 +lastmod: 2025-12-30T14:40:56+01:00 +draft: false +images: [ ] +menu: + docs: + parent: "weblogin" +type: docs +weight: 324000 +toc: true +--- + +This guide provides a step-by-step walkthrough for force-installing the WebLogin extension on Google Chrome using +Microsoft Intune. + +## Prerequisites + +- Intune Administrator permissions. + +- Windows 10/11 devices enrolled in Intune. + +- Google Chrome must already be installed on the target devices. + +## Installation Details + +- **Extension Name:** WebLogin + +- **Extension ID:** eagmgpbjpedchliifpgfgogdknnmkaej + +- **Update URL:** https://clients2.google.com/service/update2/crx + +## Step 1: Create the Configuration Profile + +1. Sign in to the [Microsoft Intune admin center](https://intune.microsoft.com/). + +2. Navigate to **Devices** > **Windows** > **Configuration**. + +3. Click **Create** > **New Policy**. + +4. Select the following: + + - **Platform:** Windows 10 and later + + - **Profile type:** Settings catalog + +5. Click **Create**. + + ![alt](/images/vendor/weblogin/weblogin_intune_profile.jpg) + +6. On the **Basics** tab, enter a name (e.g., Chrome - Force Install WebLogin Extension) and an optional description. + Click **Next**. + +## Step 2: Configure the Extension Policy + +1. On the **Configuration settings** tab, click **+ Add settings**. + +2. In the **Settings picker**, search for "Extension" and select the **Google** > **Google Chrome** > **Extensions** + category. + +3. Check the box for **Configure the list of force-installed apps and extensions**. + + ![alt](/images/vendor/weblogin/settings_picker.jpg) + +4. Close the **Settings picker**. + +5. In the configuration pane, toggle the setting to **Enabled**. + + ![alt](/images/vendor/weblogin/config_toggle.png) + +6. Under **Extension/App IDs and update URLs to be silently installed**, enter the following string exactly: + + ``` + eagmgpbjpedchliifpgfgogdknnmkaej;https://clients2.google.com/service/update2/crx + ``` + ![alt](/images/vendor/weblogin/extension_id.jpg) + +7. Click **Next**. + +## Step 3: Assignments and Review + +1. **Scope tags:** Add if your organization uses them, otherwise click **Next**. + +2. **Assignments:** Click **Add groups** and select the device or user group(s) you want to receive the extension. + +3. **Review + create:** Verify the settings and the Extension ID string. Click **Create**. + +## Step 4: Verification + +Once the policy syncs with the target devices (this can be manually triggered by going to **Settings > Accounts > Access +work or school > Info > Sync** on the device): + +1. Open **Google Chrome**. + +2. Go to `chrome://extensions`. + +3. The **WebLogin** extension should appear and show as "Installed by your administrator." + +4. You can also verify the policy status at `chrome://policy`. Look for the `ExtensionInstallForcelist` policy. diff --git a/content/en/docs/software_and_hardware/browser_extensions/weblogin/install_weblogin_on_edge_for_windows_with_intune.md b/content/en/docs/software_and_hardware/browser_extensions/weblogin/install_weblogin_on_edge_for_windows_with_intune.md new file mode 100644 index 00000000..b604e0bb --- /dev/null +++ b/content/en/docs/software_and_hardware/browser_extensions/weblogin/install_weblogin_on_edge_for_windows_with_intune.md @@ -0,0 +1,103 @@ +--- +title: "Install on Edge for Windows using Intune" +description: "" +lead: "" +date: 2025-12-30T14:40:56+01:00 +lastmod: 2025-12-30T14:40:56+01:00 +draft: false +images: [ ] +menu: + docs: + parent: "weblogin" +type: docs +weight: 323000 +toc: true +--- + +This guide provides a step-by-step walkthrough for force-installing the WebLogin extension on Microsoft Edge using +Microsoft Intune. + +## Prerequisites + +- Intune Administrator permissions. + +- Windows 10/11 devices enrolled in Intune. + +- Microsoft Edge must already be installed on the target devices. + +## Installation Details + +- **Extension Name:** WebLogin + +- **Extension ID:** eagmgpbjpedchliifpgfgogdknnmkaej + +- **Update URL:** https://clients2.google.com/service/update2/crx + +## Step 1: Create the Configuration Profile + +1. Sign in to the [Microsoft Intune admin center](https://intune.microsoft.com/). + +2. Navigate to **Devices** > **Windows** > **Configuration**. + +3. Click **Create** > **New Policy**. + +4. Select the following: + + - **Platform:** Windows 10 and later + + - **Profile type:** Settings catalog + +5. Click **Create**. + + ![alt](/images/vendor/weblogin/weblogin_intune_profile.jpg) + +6. On the **Basics** tab, enter a name (e.g., Edge - Force Install WebLogin Extension) and an optional description. + Click **Next**. + +## Step 2: Configure the Extension Policy + +1. On the **Configuration settings** tab, click **+ Add settings**. + +2. In the **Settings picker**, search for "Extension" and select the **Microsoft Edge** > **Extensions** + category. + +3. Check the box for **Control which extensions are installed silently**. + + ![alt](/images/vendor/weblogin/settings_picker_edge.jpg) + +4. Close the **Settings picker**. + +5. In the configuration pane, toggle the setting to **Enabled**. + + ![alt](/images/vendor/weblogin/config_toggle_edge.jpg) + +6. Under **Extension/App IDs and update URLs to be silently installed**, enter the following string exactly: + + ``` + eagmgpbjpedchliifpgfgogdknnmkaej;https://clients2.google.com/service/update2/crx + ``` + ![alt](/images/vendor/weblogin/extension_id_edge.jpg) + +7. Click **Next**. + +## Step 3: Assignments and Review + +1. **Scope tags:** Add if your organization uses them, otherwise click **Next**. + +2. **Assignments:** Click **Add groups** and select the device or user group(s) you want to receive the extension. + +3. **Review + create:** Verify the settings and the Extension ID string. Click **Create**. + +## Step 4: Verification + +Once the policy syncs with the target devices (this can be manually triggered by going to **Settings > Accounts > Access +work or school > Info > Sync** on the device): + +1. Open **Microsoft Edge**. + +2. Go to `edge://extensions`. + +3. You should see **WebLogin** in the list. It will have a briefcase icon next to it, indicating it is managed by your + organization. + +4. You can also verify the policy status at `edge://policy`. Look for the `ExtensionInstallForcelist` policy. diff --git a/content/en/docs/software_and_hardware/browser_extensions/weblogin_extension.md b/content/en/docs/software_and_hardware/browser_extensions/weblogin/overview.md similarity index 96% rename from content/en/docs/software_and_hardware/browser_extensions/weblogin_extension.md rename to content/en/docs/software_and_hardware/browser_extensions/weblogin/overview.md index fbd38e75..8482073b 100644 --- a/content/en/docs/software_and_hardware/browser_extensions/weblogin_extension.md +++ b/content/en/docs/software_and_hardware/browser_extensions/weblogin/overview.md @@ -1,5 +1,5 @@ --- -title: "WebLogin Extension" +title: "Overview" description: "" lead: "" date: 2024-07-20T14:40:56+01:00 @@ -8,7 +8,7 @@ draft: false images: [ ] menu: docs: - parent: "browser_extensions" + parent: "weblogin" type: docs weight: 321100 toc: true diff --git a/static/images/vendor/weblogin/config_toggle.png b/static/images/vendor/weblogin/config_toggle.png new file mode 100644 index 00000000..3d277964 Binary files /dev/null and b/static/images/vendor/weblogin/config_toggle.png differ diff --git a/static/images/vendor/weblogin/config_toggle_edge.jpg b/static/images/vendor/weblogin/config_toggle_edge.jpg new file mode 100644 index 00000000..900bde61 Binary files /dev/null and b/static/images/vendor/weblogin/config_toggle_edge.jpg differ diff --git a/static/images/vendor/weblogin/create_script.jpg b/static/images/vendor/weblogin/create_script.jpg new file mode 100644 index 00000000..5279275e Binary files /dev/null and b/static/images/vendor/weblogin/create_script.jpg differ diff --git a/static/images/vendor/weblogin/extension_id.jpg b/static/images/vendor/weblogin/extension_id.jpg new file mode 100644 index 00000000..beac1936 Binary files /dev/null and b/static/images/vendor/weblogin/extension_id.jpg differ diff --git a/static/images/vendor/weblogin/extension_id_edge.jpg b/static/images/vendor/weblogin/extension_id_edge.jpg new file mode 100644 index 00000000..50ff4718 Binary files /dev/null and b/static/images/vendor/weblogin/extension_id_edge.jpg differ diff --git a/static/images/vendor/weblogin/script_settings_chrome.jpg b/static/images/vendor/weblogin/script_settings_chrome.jpg new file mode 100644 index 00000000..66cada9f Binary files /dev/null and b/static/images/vendor/weblogin/script_settings_chrome.jpg differ diff --git a/static/images/vendor/weblogin/script_settings_edge.jpg b/static/images/vendor/weblogin/script_settings_edge.jpg new file mode 100644 index 00000000..5dc0d0bf Binary files /dev/null and b/static/images/vendor/weblogin/script_settings_edge.jpg differ diff --git a/static/images/vendor/weblogin/settings_picker.jpg b/static/images/vendor/weblogin/settings_picker.jpg new file mode 100644 index 00000000..8f862c31 Binary files /dev/null and b/static/images/vendor/weblogin/settings_picker.jpg differ diff --git a/static/images/vendor/weblogin/settings_picker_edge.jpg b/static/images/vendor/weblogin/settings_picker_edge.jpg new file mode 100644 index 00000000..92c1cd21 Binary files /dev/null and b/static/images/vendor/weblogin/settings_picker_edge.jpg differ diff --git a/static/images/vendor/weblogin/weblogin_intune_profile.jpg b/static/images/vendor/weblogin/weblogin_intune_profile.jpg new file mode 100644 index 00000000..951cc784 Binary files /dev/null and b/static/images/vendor/weblogin/weblogin_intune_profile.jpg differ