Kerberos Single Sign-On
1Kosmos uses Kerberos with Active Directory (AD) to provide seamless SSO. Users authenticated on their AD network are automatically signed in to 1Kosmos applications without re-entering credentials.
Prerequisites
Before starting, make sure you have:
Active Directory integrated with your 1Kosmos tenant, using an AD Broker user directory.
AD Broker v1.08.08 or later — required for Kerberos compatibility.
Domain Controller access — admin privileges to create service accounts and generate keytab files.
Create a Service Account in Active Directory
Open Active Directory Users and Computers (ADUC): go to Start → Run, type
dsa.msc, and press Enter.Right-click the target folder and select New → User.
Fill in the user details and set a User logon name (e.g.,
spnadmin).Set a password, uncheck User must change password at next logon, and click Next → Finish.
💡 Select Password never expires to prevent service interruptions. Rotate the password regularly for security.
Right-click the new user → Properties → Account tab.
Under Account Options, check either:
This account supports Kerberos AES 128-bit encryption, or
This account supports Kerberos AES 256-bit encryption
Click Apply.
Create a group policy to enable AES encryption on the AD server. See Windows Configurations for Kerberos Supported Encryption Type.
Configure the Service Principal Name (SPN)
Open a command prompt and run:
Example:
SPN format: HTTP/<1Kosmos tenant domain>@<REALM>
Find your Kerberos REALM
Go to Administrative Tools → Active Directory Domains and Trusts.
Your AD domain names are listed there.
Remove an SPN (if needed)
Generate the Keytab File
After running the setspn command, generate the keytab:
Example:
-out <filename.keytab>
Output keytab file name
-mapuser <AD user>
Service account created in Step 1
+rndPass
Generates a random password
-crypto AES256-SHA1
Encryption type (must match Step 1 account settings)
-ptype KRB5_NT_PRINCIPAL
Kerberos principal type
-princ <SPN>
Service principal configured in Step 2
Save the generated keytab file to a secure location. You will upload it to AdminX in the next step.
Enable Kerberos SSO in AdminX
For a new AD Broker user directory
Enable Kerberos Single Sign On under the Advanced Configuration tab when creating the AD Broker directory. See Connect to AD via Broker for details.
For an existing AD Broker user directory
Sign in to the AdminX portal as a tenant or community administrator.
Go to Directory → Directory Integrations.
Find your AD Broker user directory and click the pencil icon to edit.
Click the Advanced Configuration tab.
Enable Kerberos Single Sign On.
Under Key Tab file, click Upload and upload the keytab file generated in Step 3.
Click Save Changes.
Configure Browsers
Browsers must be configured to trust your 1Kosmos tenant for Kerberos authentication.
Firefox
Sign in to your Windows AD domain.
In Firefox, navigate to
about:config.Search for
network.n.Double-click network.negotiate-auth.trusted-uris and enter your 1Kosmos tenant domain (comma-separated if multiple).
If using Credential Delegation, also set network.negotiate-auth.delegation-uris with the same domains.
Restart Firefox.
Microsoft Edge / Google Chrome
Open Control Panel → Internet Options.
Go to the Security tab → Trusted Sites → Sites.
Add your 1Kosmos tenant URL and click Add → Apply → OK.
Configure Adaptive Authentication for Kerberos (Optional)
You can add a second factor on top of Kerberos using an adaptive authentication journey.
Kerberos
SSO using active Kerberos token only
Kerberos + Push
Kerberos token followed by push notification
Kerberos + Any OTP
Kerberos token followed by OTP from the 1Kosmos app
To configure:
Sign in to AdminX and go to Authentication → Adaptive Authentication.
Click Add new adaptive auth journey.
Enter a journey name and set user conditions.
In the Authentication dropdown, select the appropriate Kerberos method.
Click Save.
Last updated
Was this helpful?

