> 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/product-advisories/historical-notices/readers-credentials-and-locks/idemia-morpho-mso300-obsolescence-november-2022.md).

# IDEMIA (Morpho) MSO300 obsolescence - November 2022

Review MSO300 replacement options and Command Centre version requirements for MSO330 support.

Obsolescence of the MSO300 and the replacement models (depending on the version of CC)

November 2022

IDEMIA have obsoleted the currently supported Morpho MSO300 device and replacing it with a Morpho MSO330 device. Initial conversations with IDEMIA indicated that the new Morpho MSO330 device would be backwards compatible for legacy use and, should therefore work without the need for development on end.

To confirm, we have tested a Morpho MSO330 device, and have found that it does not work. We have confirmed this is this is due to the MorphoKit v5.39 library version required for the MSO330 device

Command Centre vEL8.80 and below use older MorphoKit v5.19.0 library, meaning that the new MSO330 will not work on these Command Centre versions.

We are updating the *MorphoKit* library to v5.39 for Command Centre vEL8.90, and the new MSO330 will be supported from v8.90 and above. We are also introducing the MSO1300 as a replacement for the obsolete MSO300 for customers on pre vEL8.90 Command Centre versions

<figure><img src="https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2FjxCIoNg27AxnJyTULcyB%2Fimage.png?alt=media&amp;token=0ea7bfb2-2604-4cda-ade6-17c41d11df9d" alt=""><figcaption></figcaption></figure>


---

# 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/product-advisories/historical-notices/readers-credentials-and-locks/idemia-morpho-mso300-obsolescence-november-2022.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.
