---
title: "Install the Axiad Conductor Browser Extension Component"
slug: "deploy-extension"
tags: ["Axiad Portal Extension"]
updated: 2026-06-08T20:55:46Z
published: 2026-06-08T20:55:46Z
canonical: "docs.axiad.com/deploy-extension"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.axiad.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Install the Axiad Conductor Browser Extension Component

You can manually install the Axiad Conductor Browser Extension on a single browser, or, if you want to install it on multiple users' machines, you can automate the installation using Group Policy Objects (GPOs) or a third-party IT management solution.

> [!WARNING]
> WARNING
> 
> Ensure you have the Axiad Conductor OS Bridge component installed on your machine prior to installing the Axiad Conductor Browser Extension.
> 
> 
> 
> **WARNING**
> 
> Air-gap / offline environments: If your client machines cannot reach the Chrome Web Store or Microsoft Edge Add-ons, follow the section [Install in Air-Gap (Offline) Environments Using a Self-Hosted CRX](/v1/docs/deploy-extension#install-in-airgap-offline-environments-using-a-selfhosted-crx1). This method requires Axiad Conductor OS Bridge 1.9.1 or later.

## Manually Install and Validate the Axiad Conductor Browser Extension

### Install on Google Chrome

1. Open Chrome.
2. Navigate to the [Chrome web store](https://chrome.google.com/webstore/category/extensions).
3. In the search bar, enter Axiad Conductor Browser Extension.
4. Click **Axiad Conductor Browser Extension**.

![](https://cdn.document360.io/eaa8d9cb-3eef-4690-8447-5bcaa4f4afb2/Images/Documentation/portal_store(1).png)
5. Click **Add to Chrome**. A pop-up message displays.
6. Click **Add extension**. The Axiad Conductor Browser Extension installs and displays on your Chrome extension page.
7. Browse and sign in to your Axiad Conductor site. The **MyIdentities** page displays by default.
8. Validate the extension:
  1. On the **MyIdentities** page, click **Add Identity Device**. An error message displays, informing you that the WebPCSC extension is not yet enabled.
  2. To the right of your address bar, click the **Axiad Conductor Browser Extension** icon. A pop up displays, asking for access to your smart cards.
  3. Click **Always**. The pop-up closes.
  4. Refresh the page. The Axiad Conductor Browser Extension validates.

### Install on Microsoft Edge

1. Open Microsoft Edge.
2. Click the **Extensions** icon, to the right of your browser address bar.
3. Select **Open Microsoft Edge Add-ons**.
4. In the search bar, enter **Axiad Conductor Browser Extension**.
5. Click **Get**. A pop-up message displays.
6. Click **Add extension**. The Axiad Conductor Browser Extension installs and displays to the right of your browser address bar.
7. At the top right of your Edge browser, click the **Extensions** icon.
8. To the right of the Axiad Conductor Browser Extension, click **... > Manage Extension**.

![manage_edge_extension](https://cdn.document360.io/eaa8d9cb-3eef-4690-8447-5bcaa4f4afb2/Images/Documentation/manage_edge_extension.png)

The **Extensions** page displays.
9. Enable **Allow inPrivate**.

![allow-inprivate](https://cdn.document360.io/eaa8d9cb-3eef-4690-8447-5bcaa4f4afb2/Images/Documentation/allow-inprivate.png)
10. Sign into your Axiad Conductor site. The **MyIdentities** page displays by default.
11. Validate the extension:
  1. On the **MyIdentities** page, click **Add Identity Device**. An error message displays, informing you that the Axiad Conductor OS Bridge extension is not yet enabled.
  2. To the right of your address bar, click the **Axiad Conductor Browser Extension** icon. A pop up displays, asking for access to your smart cards.
  3. Click **Always**. The pop-up closes.
  4. Refresh the page. The Axiad Conductor Browser Extension validates.

## Automatically Install and Validate the Axiad Conductor Browser Extension (Chrome)

### Automated Installation via GPO

1. Install and enable the Google Chrome policy template and Axiad Conductor OS Bridge value.
  1. Download the Google Chrome policy template from [https://dl.google.com/dl/edgedl/chrome/policy/policy_templates.zip](https://dl.google.com/dl/edgedl/chrome/policy/policy_templates.zip) and unpack the downloaded zip file.
  2. Copy the entire contents of the **Windows\admx** folder to your central store for Group Policy Administrative Template files. (The default location for this is **\*<domain.fqdn>*\SYSVOL\*<domain.fqdn>*\policies\PolicyDefinitions.**)
  3. Open the Group Policy Management Console (**gpmc.msc**).
  4. Either create a new **Group Policy Object** or open an existing one you want to edit.
  5. Navigate to either **Computer Configuration** or **User Configuration**.
  6. Browse to **Policies > Administrative Templates: Policy definitions > Google Chrome > Extensions**.
  7. Open the **Configure the list of force-installed apps and extensions** setting. The setting dialog box displays.
  8. Click **Enabled**.
  9. In the **Options** section, click **Show**. The **Show Contents** window displays.
  10. Copy the following value for Axiad Conductor Browser Extension and paste it in the **Show Contents** window: `pbabkmdefcmabmlmnkmnlcijhcgmmdnc;https://clients2.google.com/service/update2/crx `
  11. Click **OK**.
  12. Click **Apply**.
  13. Click **OK**.
2. Add new registry keys for domains you want to safelist.
  1. On your machine, navigate to either **Computer Configuration** or **User Configuration** folder.
  2. Browse to the **Preferences > Windows Settings > Registry** folder.
  3. Right-click the **Registry** folder and select **New > Registry Item**. The **New Registry Properties** dialog box displays.
  4. On the **General** tab, create the following keys for each domain you want to safelist:
    - **Hive:** HKEY_LOCAL_MACHINE
    - **Key path:** SOFTWARE\Policies\Google\chrome\3rdparty\extensions\pbabkmdefcmabmlmnkmnlcijhcgmmdnc\policy
    - **Value name:** noedit
    - **Value type:** REG_DWORD
    - **Value data:** 1 ------------------------
    - **Hive:** HKEY_LOCAL_MACHINE Key path: SOFTWARE\Policies\Google\Chrome\3rdparty\extensions\pbabkmdefcmabmlmnkmnlcijhcgmmdnc\policy\whitelist
    - **Value name:** 1
    - **Value type:** REG_SZ
    - **Value data:** Provide the domain name here (ex: *ucms.domaintest.com*)
  5. Open a command prompt.
  6. Run `gpupdate /force` on the Domain Controller at the command prompt. If your changes do not reflect immediately, you may need to wait for the next default time interval.
  7. On the client machine (domain):
    1. Open a command prompt.
    2. Run `gpupdate /force` on the Domain Controller at the command prompt.
    3. Open Chrome.
    4. Click **Extensions > More Tools** to confirm that Axiad Conductor Browser Extension is in the Chrome extension list.
    5. Navigate to the **HKLM > Software > Policies > Google > Chrome > 3rdparty > extensions > pbabkmdefcmabmlmnkmnlcijhcgmmdnc > policy > whitelist** folder to verify the registry keys you created in step 2d display.
3. Validate the Axiad Conductor Browser Extension in the Axiad Conductor.
  1. Log into your **Axiad Unified Portal**.
  2. To the right of your address bar, click the **Axiad Conductor Browser Extension** icon. A pop up displays, asking for access to your smart cards.
  3. Click **Always**. The pop-up closes.
  4. Refresh the page. The Axiad Conductor Browser Extension is now validated.

### Automated Installation via Third-party IT Management Solution

As an alternative to GPO deployments, you can deploy Axiad Portal registry settings via an automated rollout using a third-party IT management solution.

On the remote machine, execute the default registry file below to install and safelist the correct domains:

```Axiad
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\ExtensionInstallForcelist]
"1"="pbabkmdefcmabmlmnkmnlcijhcgmmdnc;https://clients2.google.com/service/update2/crx"
; WebPCSC Bridge Config (Google Chrome)

[HKEY_LOCAL_MACHINE\Software\Policies\Google\Chrome\3rdparty\extensions\pbabkmdefcmabmlmnkmnlcijhcgmmdnc\policy]
; Controls whether or not the user may influence the whitelist.
; If true (1), limit the user to only hosts whitelisted ahead of time.
; If false (0), let the user approve or deny access to any host not whitelisted ahead of time.
"noedit"=dword:00000000

[HKEY_LOCAL_MACHINE\Software\Policies\Google\Chrome\3rdparty\extensions\pbabkmdefcmabmlmnkmnlcijhcgmmdnc\policy\whitelist]

; Provides a preseeded whitelist of hosts that the WebPCSC Bridge will trust automatically.
; Create values of type REG_SZ numbering from 1 to N for as many entries as you desire.
"1"="portal-<UATstack>.demo.axiadids.net"
"2"="portal-<stack>.cloud.axiadids.net"
```

## Automatically Install and Validate the Axiad Conductor Browser Extension (Edge)

### Automated Installation via GPO

1. Using the **Group Policy Management Console** (gpmc.msc) on one of your domain controllers, open a new or existing GPO, go to **Preferences > Registry**, then right-click on **Registry**, select **New > Registry Item**:

![](https://cdn.document360.io/eaa8d9cb-3eef-4690-8447-5bcaa4f4afb2/Images/Documentation/image(33).png)

1. For each domain you want to whitelist, create a new entry with the following settings:
  - Action: **Create**
  - Hive: **HKEY_LOCAL_MACHINE**
  - Key path: `SOFTWARE\Policies\Microsoft\Edge\3rdparty\extensions\jjilfdljambeacgjgnkhjhpiijgjddjl\policy\whitelist`
  - Value name: **1** (increment with each new entry)
  - Value data: **<ucms.corp.acme.com>**
2. (optional) to prevent users from whitelisting additional domains:
  - Action: **Create**
  - Hive: HKEY_LOCAL_MACHINE
  - Key path: `SOFTWARE\Policies\Microsoft\Edge\3rdparty\extensions\jjilfdljambeacgjgnkhjhpiijgjddjl\policy`
  - Value name: **noedit**
  - Value data: **1**
3. Test/confirm your policy on a machine targeted by this group policy:
  1. Run **gpupdate /force**
  2. Open **regedit.exe** and verify the settings under **HKLM\SOFTWARE\Policies**
  3. Log into your portal and verify that the **Axiad Conductor Browser Extension** icon on the top-right turns green when a supported identity device is inserted

### Force Installation

To force the installation, you can add the following:

`[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\ExtensionInstallForcelist]`

`"1"="jjilfdljambeacgjgnkhjhpiijgjddjl"`

## Install in Air-Gap (Offline) Environments Using a Self-Hosted CRX

In air-gap or restricted networks where client machines cannot reach the public Chrome Web Store or Microsoft Edge Add-ons, you can deploy the Axiad Conductor Browser Extension from a signed CRX file hosted on your own internal web server.

Starting with version 1.9.1, the extension package includes a signed CRX file and an `update.xml` manifest, so no internet access or store connectivity is required.

**Note:** This method uses a different extension ID than the store-based installation described earlier in this article. The store builds use ID `pbabkmdefcmabmlmnkmnlcijhcgmmdnc` (Chrome). The self-hosted CRX uses the static ID `idkbfnblekadjbhjaejnbbebnjbnbfnh`. Use the ID that matches your deployment method.

### Prerequisites

- **Axiad Conductor OS Bridge 1.9.1 or later** must be installed on client machines. The CRX extension ID is registered in the OS Bridge native messaging allowed origins starting in 1.9.1; earlier versions will not communicate with this extension.
- An **internal web server** reachable by client machines, to host the CRX and `update.xml` files.
- **Administrative access** to deploy Group Policy (or edit the registry) on client machines.

### Package contents

The signed CRX and update manifest are located in a `crx/` folder inside the extension ZIP:

```plaintext
axiad-conductor-browser-extension-1.9.1.zip
├── (standard extension files)
└── crx/
    ├── AxiadPortalExtension-1.9.1.crx
    └── update.xml
```

### Host the extension files

1. Obtain `axiad-conductor-browser-extension-{version}.zip` from your Axiad-provided source.
2. Extract the ZIP and open the `crx/` folder.
3. Copy `AxiadPortalExtension-{version}.crx` and `update.xml` to an internal web server that client machines can reach over HTTPS.

### Force-install on Google Chrome

Chrome blocks manual drag-and-drop CRX installation (Chrome 75 and later), so the extension must be deployed through Group Policy.

Registry path:

```plaintext
HKLM\SOFTWARE\Policies\Google\Chrome\ExtensionInstallForcelist
```

Add a string value:

| Field | Value |
| --- | --- |
| Name | The next available number (for example, `1`) |
| Value | `idkbfnblekadjbhjaejnbbebnjbnbfnh;https://{your-server}/update.xml` |

Replace `{your-server}` with the internal server hosting your CRX and `update.xml`.

### Force-install on Microsoft Edge

Registry path:

```plaintext
HKLM\SOFTWARE\Policies\Microsoft\Edge\ExtensionInstallForcelist
```

Add a string value using the same format as Chrome:

| Field | Value |
| --- | --- |
| Value | `idkbfnblekadjbhjaejnbbebnjbnbfnh;https://{your-server}/update.xml` |

Edge supports CRX3 extensions natively, so no additional policy is required to allow extensions from outside the store when using force-install.

### Update to a new version

The `update.xml` file tells Chrome and Edge where to check for updates and which version is available. To roll out a new version, replace **both** the CRX file and `update.xml` on your internal server. Managed browsers pick up the update automatically at their next update check.