> 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-licensing-requirements.md).

# IDEMIA licensing requirements

Reference required IDEMIA reader, server, workstation, Verif, and IDENT licenses.

IDEMIA readers need a reader integration licence in Command Centre. Workstations that capture templates, and some servers, also need a Verif or IDENT licence.

### Reader integration licence (Part 2A8951)

A **MORPHO (IDEMIA) Reader Integration licence (Part No. 2A8951)** is required **per** IDEMIA fingerprint, finger-vein, or Wave wall-mounted reader configured in Command Centre. It is **not** required for enrolment readers.

* Supplied **at no charge** with Morpho readers bought from Gallagher.
* Licensed on a **per Morpho reader** basis.
* **Not included** in SMA licence charges.

A site installing a Morpho reader bought from a **third party** (not Gallagher) needs the 2A8951 licence purchased separately.

### Workstations

Workstations capturing templates for cardholders need a **Verif Dongle** or **Software Verif Licence** installed at that workstation, plus License Manager and dongle drivers.

{% hint style="warning" %}
**C864510 MORPHO V2 USB VERIF DONGLE is now obsolete.** The new Software Verif licence is **C864662 IDEMIA SOFT VERIF LICENSE**.
{% endhint %}

IDEMIA's guide *How to Retrieve Host ID and Install Software License on Windows* covers installing the Software Verif 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.3.0** on this page, and **6.1.0** on [Verif licenses and dongle variants](/knowledge-hub/products/integrations/third-party-readers/idemia-morpho/reference/idemia-morpho-verif-license-and-dongle-variants.md). The enrolment readers page says to use the latest, v6.3.0. Both values are shown until this is confirmed.
{% endhint %}

Gallagher also offers bundles of MSO devices with Verif licences attached:

| Gallagher part | IDEMIA part | Bundle                        |
| -------------- | ----------- | ----------------------------- |
| **C864666**    | 293670375   | 1 MSO 330 with Verif License  |
| **C864667**    | 293670362   | 1 MSO 1300 with Verif License |

The dongle and licence variants, and how the Software Verif licence is ordered: [Verif licenses and dongle variants](/knowledge-hub/products/integrations/third-party-readers/idemia-morpho/reference/idemia-morpho-verif-license-and-dongle-variants.md).

### Server licensing

* Pre-**vEL7.80** needs a **Verif Dongle and MACI licence** on the server, for communication with the IDEMIA biometric readers.
* **vEL7.80+** does **not** need a server Verif dongle.
* The server needs License Manager and the dongle drivers installed.

### Duplicate template detection

For the **Duplicate Detection** feature (Duplicate Template Detection) to work, the server needs an **IDENT Dongle and IDENT Licence**.

To extend a reader's template database with an extended database licence, see [Extend an IDEMIA reader database](/knowledge-hub/products/integrations/third-party-readers/idemia-morpho/configure/idemia-readers-morpho-extended-licenses.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-licensing-requirements.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.