> 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/licensable-features/entra-id-single-sign-on.md).

# Entra ID Single Sign-on

### Introduction

Entra ID Single Sign-on is a licensable feature, i.e. your licence file must contain the option:

`[Features]`\
`EntraIDSingleSignOn=1`

OR

`[Features]`\
`EntraIDSync=1`

Single Sign-on refers to the ability to use an Entra ID credential for logging onto one or more applications. Command Centre supports the ability for the system to automatically log an operator onto Command Centre Client using their Entra ID credential, when it is launched. Configuration Client does not support logon using Entra ID Single Sign-on.

***

### Benefits of an Entra ID integration

* A reduction in the number of usernames and passwords people have to remember.
* It allows sites to take advantage of Entra ID logon management for the purpose of logging onto Command Centre. Entra ID allows for the specification of more complex rules for passwords (than is currently available for Command Centre), and can require a combination of authentication methods including biometrics.
* The ability to prevent people from logging on to other applications by disabling their account in a central place (i.e. Entra ID).
* Entra ID credentials can be synced to Command Centre operator accounts using the separately licensed Entra ID Sync feature, reducing manual operator configuration. The Entra ID Sync license also includes the Entra ID Single Sign-on license. For details about this feature, contact the Gallagher Support Team.

***

### Considerations

* **Supported clients:** Entra ID Single Sign-on can only be used for logging onto the Command Centre Client and Visitor Management Kiosk (not Configuration Client). Operators must continue to log onto Configuration Client via Command Centre Client or using other authentication methods.
* **Registry configuration:** The site’s Entra ID tenant details must be manually entered in the registry on the Command Centre server.
* **Single tenant:** A Command Centre server can only connect to one app registration of one Entra ID tenant.
* **Multi-server:** If your site is using multi-server, all servers must be licensed for Entra ID Single Sign-on and connect to the same Entra ID tenant and app registration.
* **Windows accounts:** When an operator logs onto Command Centre using Entra ID Single Sign-on, their Entra ID account details are cached to the Windows account they are using, so they do not need to enter their Entra ID account details every time they log onto Command Centre. This means multiple operators with different Entra ID accounts cannot use Entra ID Single Sign-on using the same Windows account. To remove the cached Entra ID account from a Windows account, log onto the machine as the Windows account and delete the following file:

  `%LocalAppData%\Gallagher\Command Centre\SSOToken.cache`
* **Proxy:** Gallagher suggests that Entra ID Single Sign-on will work using a proxy if:
  * the proxy is configured at the machine level (e.g. via Group Policy) so that services running as Network Service or Computer Account inherit proxy settings, or
  * a dedicated Service Account with the correct user-level proxy settings is used to run the Command Centre service.

**Note:** The Command Centre Cloud's proxy is not used for this.

***

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) [Configuring Entra ID Single Sign-on and Automatic logon](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/entra-id-single-sign-on/configuring-entra-id-single-sign-on-and-automatic-logon.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) [Entra ID admin center configuration](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/entra-id-single-sign-on/entra-id-admin-center-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) [Linking operators to their Entra ID account](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/entra-id-single-sign-on/linking-operators-to-their-entra-id-account.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) [Migrating from Active Directory Single Sign-on](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/entra-id-single-sign-on/migrating-from-active-directory-single-sign-on.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/licensable-features/entra-id-single-sign-on.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.
