For the complete documentation index, see llms.txt. This page is also available as Markdown.

Set up Active Directory single sign-on

Enable Active Directory Single Sign-On and configure Service Principal Name permissions.

AD Single Sign-On lets operators log into Command Centre with their Active Directory (Windows) credentials instead of a separate CC logon. Enabling it makes Command Centre register the GGLCCSvc Service Principal Name (SPN) for the FT Command Centre Service, so Kerberos can authenticate operators. It requires the ADSingleSignOn licence feature.

This is an operator authentication feature. It is separate from, but used by, the sync integrations: the AD Sync and Entra ID Sync v1.0 configuration UIs rely on AD SSO to authorize the operator who launches them.

Step 1 — Verify the licence feature

In Server Properties > Licensing > Features, confirm ADSingleSignOn is listed and Enabled. If not, contact your Regional Support Team to request activation.

Step 2 — Enable SSO in Operator Defaults

In Server Properties > Operator Defaults, tick Enable Active Directory single sign-on. When enabled, the account used by the FT Command Centre Service attempts to register the GGLCCSvc SPN.

Permissions required

Coordinate with the site's IS team. On the domain service account (or the host machine's Computer object, if the service runs as Local System / Network Service), under Security, set both Read public information and Write public information to Allow.

AD Users and Computers — the domain service account's Security tab with Read/Write public information set to Allow

If the Command Centre service runs as Local System / Network Service, apply the same Read/Write public information permissions on the Computer object instead:

The Command Centre server Computer object properties, Security tab, with Read/Write public information allowed

How the SPN works

An SPN is a unique identifier of a service instance, used by Kerberos to associate a service instance with its logon account. When Enable Active Directory single sign-on is turned on, Command Centre automatically adds GGLCCSvc as an SPN of the Command Centre server's Computer account. This works when the FT Command Centre Service runs as Local System.

⚠️ If the FT Command Centre Service "Log on as" account is changed from Local System account to This account, SSO can fail unless the SPN is valid. GGLCCSvc must then be registered against the service account used on the service's Log On tab, and removed from the Computer account. If it remains on both there is a duplicate and SSO fails.

Registration under a service account normally requires domain-admin privileges (standard accounts cannot register SPNs). Two things to remember:

  • Disabling then re-enabling SSO makes Command Centre add GGLCCSvc back against the Computer account, re-creating a duplicate.

  • SPN changes do not take effect immediately. Reboot after deleting or adding SPNs.

How single sign-on works

Single sign-on lets a Windows user name and password log onto one or more applications. Command Centre can connect to a site's Active Directory, which:

  • lets the site use Windows logon management to log onto Command Centre, with the more complex login credentials Windows allows;

  • lets the site stop people logging on to other applications by disabling their account in one central place (Active Directory).

Licence: a licensable feature; the licence string is ADSingleSignOn=1 (Feature).

The Gallagher SSO integration uses the Kerberos V5 protocol, most of which is implemented at the Windows level. Kerberos is a network authentication protocol that works on the basis of tickets, so that nodes communicating over a non-secure network can prove their identity to one another securely.

  • Kerberos v5 is used between the Command Centre server and Active Directory.

  • The client asks Windows for a Kerberos token (which it obtains from AD) and passes it to the Command Centre server at logon, in place of the user name and password. It goes over the usual client protocol: for example OPC UA for Premier/Kiosk, or DCOM-over-WebSockets for the Configuration Client.

  • The server asks Windows to resolve the token to a domain account, then looks for a Command Centre operator linked to that account's SID. If it finds one it creates a session as that operator; otherwise it returns an error.


🔗 Related

Last updated

Was this helpful?