> 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/active-directory-single-sign-on/configuring-single-sign-on-and-automatic-logon.md).

# Configuring Single Sign-on and Automatic logon

The following configuration is required in order for an operator to be logged on automatically using their Active Directory user name and password:

* The server connected to the workstation they are launching the application from has to be enabled for Active Directory Single Sign-on.

  Refer to [Operator Defaults](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/operator-defaults.md) for the procedure.
* The operator's Cardholder record needs to be configured with their Windows logon.

  Refer to [Linking operators to their Active Directory account](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/active-directory-single-sign-on/linking-operators-to-their-active-directory-account.md) for the procedure.

**Notes:**

* Where the server, workstation and Windows user are in different domains, trust relationships need to be established between these domains in order for single sign-on to work. The trust relationship type must be Forest, not External. This is the responsibility of the company's IS department.
* There is an issue if the Command Centre service has been changed to logon using a different account from the default of local system.

  Technical Document 13778 has details on this procedure. This is available by logging into the Gallagher Security support site and navigating to **Technical Documents**. Alternatively, you can contact Gallagher Technical Support for assistance.


---

# 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/active-directory-single-sign-on/configuring-single-sign-on-and-automatic-logon.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.
