> 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/active-directory-cardholder-synchroniz.md). # Active Directory Cardholder Synchronization product update — July 2021 Understand the 2021 Active Directory Cardholder Sync architecture and upgrade changes. The Active Directory Cardholder Synchronization integration synchronizes cardholders between Microsoft Active Directory and Gallagher Command Centre. It allows creation, modification, and deletion of both user details and access permissions, and it links physical access permissions to logical access rights. The solution was updated to simplify configuration and move the back-end architecture to the REST API. The project had two main goals: * Create a solution **independent of the Command Centre version**, so it no longer needs to be upgraded each time a Command Centre server is upgraded. * Simplify configuration and installation by **removing the need to edit XML files**. ## Upgrading to Command Centre v8.50 with AD Cardholder Sync v8.50 AD Cardholder Sync was scheduled for release at the end of July 2021. From v8.50 the AD Cardholder Sync solution includes **Active Directory SSO** functionality and **no longer requires an additional workstation licence**. Configuration changes are required for this release. Once implemented, AD Cardholder Sync is independent from Command Centre, so Command Centre can be upgraded without affecting the AD Cardholder Sync installation. The source advisory also referenced an "Active Directory Sync Upgrade Summary (v8.50)" attachment and a beta release of AD Sync v8.50.178 shared on the Gallagher Box portal. Neither is reproduced here. *** 🔗 **Related** * [Product Advisories](/knowledge-hub/products/product-advisories.md). The full register of obsolescence, security, and deprecation notices. --- # 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/active-directory-cardholder-synchroniz.md?ask=&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.