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

Active Directory single sign-on common faults and scenarios

Resolve common Active Directory Single Sign-On faults, including SPN and logon-name issues.

1. SPN registration fails silently (insufficient privileges)

The domain service account lacks rights to register the SPN. Symptom: silent failure (especially pre-8.00); trace logs show a failed SPN update, for example Failed to update account SPN: 8344.

Fix: with local IT, add Read/Write public information to the domain service account and ensure it is a member of Domain Users (or apply the same permissions to the Gallagher Server Computer object for a local service account).

2. Domain policy issues

  • Kerberos encryption not allowed — error 8009030c. Enable Kerberos encryption for the operator account (the account's Support Kerberos AES 128/256 bit encryption options):

Operator account properties, Account tab, with "This account supports Kerberos AES 128/256 bit encryption" ticked
  • Certificate problem — error 8009030e ("No credentials are available in the security package"). Investigate certificate issues. This surfaces as a Directory Service Event 1220 (LDAP Interface) warning:

Windows Event Viewer showing Directory Service Event 1220 — "LDAP over SSL will be unavailable... Error value: 8009030e No credentials are available in the security package"

3. Incorrect GGLCCSvc SPN registration

GGLCCSvc must be registered to the service account the Command Centre service runs under. Common errors: registered on multiple instances, registered to the host machine instead of the service account, registered to the wrong account, or the wrong format. Guideline: Local System / Network Service → SPN under the host machine; otherwise → under the service account.

4. User logon name vs pre-Windows 2000 logon name mismatch

If an operator's User logon name and User logon name (pre-Windows 2000) differ, Command Centre may return "The Operator's Windows Logon name is not a valid logon name."

Field
Example value

User logon name

test.login@tstest.local

Pre-Windows 2000 logon name

tstest\test.login2

Active Directory account properties showing a User logon name of test.login@tstest.local but a pre-Windows 2000 name of TSTEST\test.login2

Observed behaviour (SSO enabled): the search (three dots next to the Windows logon field) returns the user, but clicking OK sets the Windows logon to tstest.local\test.login, the wrong value; only tstest.local\test.login2 logs in successfully.

Command Centre operator search returning the user test.login@tstest.local via Check Names
The operator's Windows logon field populated with the incorrect tstest.local\test.login value after clicking OK

Workaround: manually enter the correct pre-Windows 2000 logon name (tstest.local\test.login2) in the Windows logon field. This allows both saving and successful login.


🔗 Related

Last updated

Was this helpful?