> 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/configure/idemia-readers-disabling-biometric-on-card-at-the-morpho-reader.md).

# Disable biometric authentication for a card

Configure MBTB settings for card-only access on IDEMIA (Morpho) biometric readers.

You can disable biometric on a card encoded with the Morpho MIFARE object set to **Card Number + Biometric**, **without re-encoding** it to Card Number only. Change the configuration keys below in MBTB (Biobox Toolbox) for card-only user authentication. Click the green tick to apply each change.

{% hint style="warning" %}
This is done **per reader**, one reader at a time. There is no quick way to apply it to multiple readers.
{% endhint %}

The keys depend on the reader and its protocol: Legacy protocol (MA100/120, MA J, MA520, OMA520), Native MA5G (Sigma Lite, Sigma, Extreme), or Sigma in Legacy MA2G.

### Legacy protocol readers

This applies to **MA100/120, MA J Series, MA520 and OMA520** readers only. It does **not** apply to MA Sigma range readers in Legacy mode (MA2G).

* `app/bio ctrl/bypass authentication` = `1` (default = `0`)

### Native mode (MA5G) Sigma readers

This applies to MA Sigma readers: MA Sigma Lite, MA Sigma and MA Sigma Extreme.

* `ucc.Finger_bio_auth_rule=0` (default = `0`)
* `ucc.per_user_rules=0` (default = `1`)
* `ucc.trigger_event=3` (default = `3`)

### Sigma readers in Legacy mode (MA2G)

This applies to MA Sigma Lite, MA Sigma and MA Sigma Extreme readers in Legacy mode. Change these configuration keys:

* `app/bio ctrl/authent card mode` = `0`
* `app/bio ctrl/authent ID contactless` = `0`
* `app/bio ctrl/authent PK contactless` = `1`
* `app/bio ctrl/bypass authentication` = `1`

To confirm reader behaviour after the change, see [Collect IDEMIA diagnostic logs](/knowledge-hub/products/integrations/third-party-readers/idemia-morpho/troubleshoot/idemia-readers-diagnostic-logs-from-a-morpho-reader.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/configure/idemia-readers-disabling-biometric-on-card-at-the-morpho-reader.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.