> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/integrations/third-party-readers/idemia-morpho/reference/idemia-morpho-verif-license-and-dongle-variants.md).

# Verif licenses and dongle variants

Reference IDEMIA Verif software licenses, USB dongles, parts, and workstation requirements.

{% hint style="warning" %}
**C864510 (MORPHO V2 USB VERIF DONGLE) is obsolete (12/2024).** The replacement is **C864662 (IDEMIA SOFT VERIF LICENSE)**.
{% endhint %}

{% hint style="info" %}
VisionPass and VisionPass SP need **no** Verif licence or dongle for enrolment. Wave and finger template capture **does** need a Verif dongle.
{% endhint %}

* **Software Verif Licence (C864662):** generated by IDEMIA and **locked to the workstation HOST ID** (derived from CPU, motherboard, and NIC; a docking-station NIC change can change the HOST ID). Provide the HOST ID to SOM when ordering. IDEMIA returns it (in around 2 working days or less), then it is emailed to the Channel Partner. It **cannot be shared** and is valid only for the PC it was created for.
* **MSO-with-Verif bundles:** **C864666** (MSO330) and **C864667** (MSO1300, recommended if the enrolment workstation is a **virtual machine**).
* **SafeNet Dongle ("V1"):** USB VERIF **C864401**, USB IDENT **C864403/C864405**. A 5-digit serial that needs a matching **MACI** licence in License Manager, and Morpho License Manager 4.10+. Required for Command Centre **7.70 and below** (works with 7.80+).
* **Morpho ACS Dongle ("V2"):** V2 USB VERIF **C864510** (obsolete), USB IDENT **C864515**. A SIM with the MACI licence pre-injected (the SIM must be inserted).

### Software Verif Licence

Because of component shortages, **C864510 MORPHO V2 USB VERIF DONGLE**, used for biometric enrolment at Command Centre workstations, is obsolete. **C864662 IDEMIA SOFT VERIF LICENSE** was introduced so customers can keep enrolling at Command Centre workstations.

* IDEMIA generates the licence and locks it to the **HOST ID** of the enrolment workstation. Provide the HOST ID to **SOM (Sales Order Management)** when you order C864662. The process is similar to ordering a reader database expansion licence, which needs the reader License ID.
* When SOM receives the licence back from IDEMIA, it is emailed to the Channel Partner. Lead time is expected to be **no more than 2 working days**.
* The HOST ID is based on the computer hardware, including the **CPU, motherboard and network card**. If a laptop uses a docking station with a network card, changing the docking station can change the HOST ID.

{% hint style="warning" %}
The Software Verif licence **cannot be shared**. It is only valid for the PC it was created for.
{% endhint %}

IDEMIA's guide *How to Retrieve Host ID and Install Software License on Windows* covers getting the HOST ID and installing the licence. The Software Verif licence needs **Multiprotect License Manager**.

{% hint style="warning" %}
Gallagher sources give two versions of Multiprotect License Manager as required for the Software Verif licence: **6.1.0** on this page, and **6.3.0** on [IDEMIA licensing requirements](/knowledge-hub/products/integrations/third-party-readers/idemia-morpho/reference/idemia-morpho-licensing-requirements.md). The enrolment readers page says to use the latest, v6.3.0. Both values are shown until this is confirmed.
{% endhint %}

### MSO with embedded Verif licence

These bundled part numbers each include one MSO USB desktop enrolment reader loaded with a Verif licence:

* **C864666** IDEMIA MSO330 with Verif License Bundle.
* **C864667** IDEMIA MSO1300 with Verif License Bundle.

{% hint style="info" %}
**C864667** is recommended if the enrolment workstation is a **virtual machine**.
{% endhint %}

### Verif dongles

| Dongle                                              | Part numbers                                                        | Identifying feature                                                                  | License Manager                           | Command Centre                                                  |
| --------------------------------------------------- | ------------------------------------------------------------------- | ------------------------------------------------------------------------------------ | ----------------------------------------- | --------------------------------------------------------------- |
| **SafeNet Dongle** (referred to as a **V1** dongle) | USB VERIF **C864401** · USB IDENT **C864403/C864405**               | 5-digit serial number; needs a **matching MACI licence** loaded into License Manager | Morpho License Manager **4.10+**          | **Required for 7.70 and below** (but works with 7.80 and above) |
| **Morpho ACS Dongle** (**V2**)                      | V2 USB VERIF **C864510** (obsolete 12/2024) · USB IDENT **C864515** | Has a **SIM card with the MACI licence already injected**                            | **ONLY** Morpho License Manager **4.13+** | **7.80 and above** (will **not** work on 7.70 and earlier)      |

{% hint style="warning" %}
**V2 dongle:** insert the SIM in the **correct orientation**, as marked on the dongle. Otherwise the dongle does not show in Morpho License Manager.
{% endhint %}

**New Verif dongle (2021):** released into the market in late 2021 as a standard Verif dongle for workstation capturing. Use the **ACS drivers version 4.0.0.7** included on the Gallagher install media.

### Dongle compatibility

* **SafeNet** dongles are compatible with Morpho License Manager **v4.10 and above**. License Manager v4.10 is packaged in the Command Centre **vEL7.80 to vEL8.00** install media.
* **Morpho ACS (V2)** dongles are compatible with Morpho License Manager **v4.13 and above**. License Manager v4.13 is packaged in the Command Centre **vEL8.10** install media.
* Morpho License Manager **v4.13 works with Command Centre vEL7.80 to vEL8.00**.

### Which dongles and licences you need

| Command Centre                         | Server                          | Workstation encoding fingerprints |
| -------------------------------------- | ------------------------------- | --------------------------------- |
| **Prior to 7.80**                      | Software + Dongle + MACI        | Software + Dongle                 |
| **7.80 and later** (MACI not required) | Nothing other than the software | Software + Dongle                 |

When each licence is required: [IDEMIA licensing requirements](/knowledge-hub/products/integrations/third-party-readers/idemia-morpho/reference/idemia-morpho-licensing-requirements.md).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/products/integrations/third-party-readers/idemia-morpho/reference/idemia-morpho-verif-license-and-dongle-variants.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
