> 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/configuration-client/integrated-systems/morpho-biometric-integration.md).

# Morpho Biometric Integration

### Introduction

The term biometric operation refers to the process of evaluating a biometric sample, (e.g. a person’s fingerprint) for the purpose of authenticating a person’s identity. Typically, a biometric sample is taken from a person and compared with one or more previously-captured biometric samples, called templates, to determine or verify that person’s identity. The Biometric Integration feature provides the ability for Morpho biometric readers to be connected to Gallagher Command Centre and configured as hardware items, for the purpose of biometric identification.

There are several procedures that make up the process for configuring Biometric Integration, both within Gallagher Command Centre and externally from the Gallagher Command Centre system, (e.g. physically installing and configuring MorphoAccess readers).

This chapter covers the entire configuration process from start to finish.

**Notes:**

* If your site wants full CAPSS compliance (and has `NPSA=1` in the license file), Morpho should not be installed, otherwise your site will not comply with CAPSS 2024.
* MA2G readers are no longer supported from Command Centre vEL9.30 or later.

***

### Biometric categories

Biometric operations fall into one of two different categories depending on how many templates a person's biometric sample is compared with during the operation, as follows:

**Biometric Identification:**

When a person's biometric sample, (e.g. their fingerprint or finger vein), is compared against all the fingerprints/veins in a database to determine who that person is, the biometric operation is called "biometric identification" because it has been used to identify who that person is.

**Biometric Verification:**

When a person identifies themselves prior to the biometric operation, (e.g. badging their card), and then the biometric operation is used to verify that the person is in fact who they say they are, this is called "biometric verification". This is done by comparing the biometric sample presented with just one template that has been previously identified as belonging to that person.

If a site chooses to control access by way of biometric identification (as opposed to biometric verification), then there is no need for a Cardholder to carry or use a card. However, if a site chooses to control access by way of biometric verification, then typically these Cardholders will carry a card that they will use to first identify themselves prior to a biometric operation verifying they are who they say they are.

***

### Morpho Biometric Readers

Morpho Biometric Readers can capture a fingerprint from a Cardholder and compare it with a biometric template to determine how closely it matches. The results of that biometric operation can then be used to determine with more certainty that the cardholder is who they say they are.

#### Biometric Templates

When using biometrics for access control, the enrolment process encompasses three steps:

* Acquisition of the biometric image
* Conversion of the biometric image to a template (a mathematical representation of the biometric image)
* Storage of the template for authentication or identification purposes. Biometric images are not stored at enrollment or matching stations.

The biometric templates are stored as reference templates. A template is a set of 0’s and 1’s created using a mathematical formula that is patented called a template generator. It is not possible to reverse engineer the 0’s and 1’s or the mathematical representation of the biometric back to the biometric image. Images are converted to proprietary templates using a proprietary algorithm and are stored in a database located in the Biometric reader. The database of reference templates is encrypted using AES 256.

#### Display messages

Gallagher's Morpho Biometric Integration allows messages to be displayed on OSDP Morpho Biometric readers with LCD screens. If reader display messages are enabled, the current date and time, and the door's or Access Zone's status, are displayed on the screen when the reader is idle. Additionally, access granted and descriptive access denied messages are displayed when a finger, hand, face or card is presented at the reader. If two readers are assigned to the same Exit Zone or Entry Zone of a Door - one OSDP and Wiegand - a Cardholder badging at the Wiegand reader will result in the more descriptive access message being displayed on the OSDP reader (as well as the regular message on the Wiegand reader).

Several default messages will display. [Click here](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/open-supervised-device-protocol-osdp-integration/list-of-displayed-messages.md) to see the messages that are displayed by default. If your site requires these messages to be changed, including whether the date and/or time are displayed, contact the Gallagher Support Team.

***

Select the item below that you require further detail on:

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Installation](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/morpho-biometric-integration/installation.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Installing MorphoAccess Readers](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/morpho-biometric-integration/installing-morphoaccess-readers.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Enrolling Users](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/morpho-biometric-integration/enrolling-users.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Communications Encryption](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/morpho-biometric-integration/communications-encryption.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Configuring Biometric Verification](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/morpho-biometric-integration/configuring-biometric-verification.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Encoding Morpho Cards for Verification](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/morpho-biometric-integration/encoding-morpho-cards-for-verification.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Performing Overrides on a Morpho Biometric Reader](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/morpho-biometric-integration/performing-overrides-on-a-morpho-biometric-reader.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Morpho OSDP Configuration](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/morpho-biometric-integration/morpho-osdp-configuration.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [QR Code authentication mode at Morpho Readers](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/morpho-biometric-integration/qr-code-authentication-mode-at-morpho-readers.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Troubleshooting](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/morpho-biometric-integration/troubleshooting-morpho-biometrics.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Appendix: Tamper prevention bypass for IDEMIA VisionPass](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/morpho-biometric-integration/appendix-tamper-prevention-bypass-for-idemia-visionpass.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/configuration-client/integrated-systems/morpho-biometric-integration.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.
