> For the complete documentation index, see [llms.txt](https://docs.bluefletch.com/bluefletch-enterprise/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluefletch.com/bluefletch-enterprise/product-guides/bluefletch-launcher-for-windows/getting-started/installation/bfe-agent-extension.md).

# BFE Agent Extension

BFE Agent is an Edge/Chrome browser extension required for NFC + PIN Login. It automates the login process after a user badge and PIN are verified.

This page contains information to install the extension via Admin Chrome or GPO. Hosting the extension is required for both options. 

### <mark style="color:$primary;">Step 1: Hosting Extension Update file</mark>

The update.xml file is required for distributing the extension in Chrome or Edge.

1. Create `update.xml` file pointing to the target extension version.
   1. **Extension ID** and **CRX file URL** will be provided by BlueFletch.

```
<?xml version='1.0' encoding='UTF-8'?>
<gupdate xmlns='http://www.google.com/update2/response' protocol='2.0'>
  <app appid='<EXTENSION-ID>'>
    <updatecheck codebase='<CRX-FILE-PATH>' version='1.1' />
  </app>
</gupdate>
```

2. Host the `update.xml` file.

### <mark style="color:$primary;">Step 2: Distribution</mark>

#### Distribute Chrome Extension via Admin Console

1. Go to <https://admin.google.com/>
2. Navigate to Devices > Chrome > Apps & extensions > Users & browsers.
3. Select the organizational unit (OU) you want to target.
4. Tap "+" to add an extension.
5. Specify the extension ID and update/install URL and make sure to set it to **force-install**.
   1. Use the extensionId provided by BlueFletch and updatedURL you are hosting.
   2. This will cause the extension to be automatically installed and the user cannot remove.

#### Distribute Edge Extension via Group Policies

The following steps outline how to use GPO for force installation.

1. **Open Group Policy Management Editor:** On your domain controller, open the [Group Policy Management](https://learn.microsoft.com/en-us/deployedge/microsoft-edge-manage-extensions-policies) tool or the local Group Policy Editor.
2. **Navigate to the Extensions Policy:** Go to **Computer Configuration** > **Policies** > **Administrative Templates** > **Microsoft Edge** > **Extensions**.
3. **Enable the Force-Install Policy:** Open the policy setting named **Control which extensions are installed silently** (registry key: `ExtensionInstallForcelist`).
4. **Add Extension Details:**
   * Select **Enabled**.
   * Click the **Show** button to open the list of extensions.
   * In the list, enter the extension ID and the updatedURL in the format: `extensionID;updateURL`.
     * Use the extensionId provided by BlueFletch and updatedURL you are hosting.
   * Example: `dcammpemjaodphbdhpcmlfhbgkhagalj;https://edge.company.cloudapp.azure.com/cases/extension/updates.xml`
5. **Apply the Policy:** Click **OK** and then **Apply**. The policy will be applied to target devices, and the extension should install automatically the next time Edge is opened (after policies are refreshed).&#x20;

#### Force Installation Edge Extension via Microsoft Intune&#x20;

Alternatively, if you are using Microsoft Intune for device management, you can configure the policy there:&#x20;

1. In the Microsoft Intune admin center, navigate to **Devices** > **Scripts** or **Configuration profiles**.
2. Create a new configuration profile for Windows 10 or later.
3. Add the **Control which extensions are installed silently** setting under the **Microsoft Edge** > **Extensions** category and specify the extension ID and update URL string as described above.&#x20;

### <mark style="color:$primary;">Verify Extension Installation</mark>

* Confirm that the BFE Agent extension appears in the corresponding browser:
  * Edge: `edge://extensions`
  * Chrome: `chrome://extensions/`


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.bluefletch.com/bluefletch-enterprise/product-guides/bluefletch-launcher-for-windows/getting-started/installation/bfe-agent-extension.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.