This documentation supports the 9.1 version of Remedy Single Sign-On.

To view the latest version, select the version from the Product version menu.

Kerberos authentication process

This topic was edited by a BMC Contributor and has not been approved.  More information.

Remedy Single Sign-On (Remedy SSO) supports Kerberos authentication starting from the release 9.1.01. The following image shows the tasks that you need to perform to configure the Kerberos authentication in Remedy SSO.


Configuring Active Directory

To configure Active Directory, perform the following steps:

#StepPerformed by
1Create a service account in Active DirectoryActive Directory administrator
2Add an SPN mapping for the service accountActive Directory administrator

(Optional) Generate a keytab file if you want to provide the credentials through a keytab file 

User who access to a server with the domain controller

Creating a service account in Active Directory

  1. Go to Active Directory.
  2. Right-click Users > New > User.
  3. Enter the user name and the user logon name in the First name and User logon name fields.
  4. Click Next.
  5. Enter user password in the Password and Confirm password fields.
  6. Select the User cannot change password and Password never expires check boxes.
  7. Click Next.
  8. Click Finish.

Adding an SPN mapping for the service account

Before you begin

  • Ensure that you have the user name and password for the service account.
  • Ensure that you have the machine name where Remedy SSO server runs.

To add an SPN mapping

To add an SPN mapping, run the setspn command on one of the directories in the Active Directory machine.

setspn -S HTTP/<HOST> <USER> 

For more information about the setspn command parameters, see the following list:

  • <HOST>: Fully qualified domain name of the host on which Remedy SSO server runs including the internet domain.

  • <REALM>: Name of the Kerberos realm.
  • <USER>: Logon name of the service account.

For example,

setspn -S HTTP/ remedyssoservice

(Optional) Generating a keytab file 

A keytab contains the Service Principle Name (SPN) credentials for Remedy SSO to communicate with the domain controller. The clients use the SPN to request a service ticket during the authentication process.

Before you begin

  • Obtain the user name and password for the service account.
  • Obtain the machine name where Remedy SSO server runs.
  • Ensure that you have appropriate administrative permissions to run the ktpass command.

To generate a keytab file

To generate a keytab file, run the ktpass command on the command line interface in an appropriate directory. The command automatically assigns HTTP/<host> SPN to the user.

ktpass /out <FILE> /princ HTTP/<HOST>@<DOMAIN> /pass <PASSWORD> /crypto ALL /ptype KRB5_NT_PRINCIPAL /Target <DOMAIN> /kvno 0

For more information about the ktpass command parameters, see the following list:

  • <FILE>: Name of the keytab file that is to be generated.
  • <HOST>: Fully qualified domain name of the host on which Remedy SSO server runs including the internet domain.
  • <DOMAIN>: Active Directory domain name written in uppercase.
  • <PASSWORD>: Password of the user.

For example,

ktpass /out c:\remedyssoservice.keytab /princ HTTP/ /crypto ALL /pass RemedySs0service /ptype KRB5_NT_PRINCIPAL /Target RSSO.COM /kvno 0

Configuring the Kerberos authentication

Before you begin 

  • Ensure that you have performed the Remedy SSO server configuration. For more information on server configuration, see Remedy SSO server general configuration.
  • Configure a realm for the authentication. For more information on realm configuration, see Configuring Realms.
  • Obtain the following information:
    • Machine name of the Key Distribution Center.
    • Kerberos realm created for Remedy SSO on Key Distribution Center.
    • Service account name for Remedy SSO.
    • Service account password if SPN credential type is to be used.
    • Keytab file if keytab credential type is to be used.

To configure the Kerberos authentication

  1. In the left navigation panel of the Add Realm or Edit Realm page, click Authentication.

  2. In the Authentication Type field, click KERBEROS.

  3. (Optional) Select the Enable AR authentication for bypass check box to enable bypass URL to authenticate against AR. For more information about enabling BMC Remedy AR System authentication for bypass, see Enabling AR authentication for bypassing other authentication methods.

  4. Enter the Kerberos details. For more information on parameters, see Kerberos authentication parameters.

  5. Click Test to verify the settings.
  6. (Optional) Click Enable Chaining Mode to enable authentication chaining and perform the following steps. For more information about the authentications that you can chain with LDAP, see Authentication chaining.
    1. Click Add Authentication.
    2. Select the required authentication type and enter the authentication details.
    3. Repeat Step a through Step b to add more authentications for the realm.

Kerberos authentication parameters


KDC Server

Name of the machine where Active Directory is hosted.

Example: ker.114kdc.local

Kerberos Realm

Name of the Kerberos realm. You must enter the realm in upper case.
Example: RSSO.COM

Service Principal Name (SPN)

  • If keytab is used, provide the full form of the SPN. For example, HTTP/
  • If keytab is not used, specify the login name of the integration user.
Credential Type

Credential type to be used by the Remedy SSO server to log on to Active Directory. Select one of the following:

  • SPN Password
  • Keytab File
SPN PasswordPassword for the service account. This field is available only if you select SPN Password in the Credential Type field.
Keytab File

Path to the keytabfile. This field is available only if you select Keytab File in the Credential Type field.

In a Remedy SSO server cluster environment, each Remedy SSO server node must contain the samekeytabfile andkeytabfile path.

UserId Format

Select one of the following formats from the list to transform the user id after a successful login.

  • user - Retains the User ID
  • user@domain - User ID with the Kerberos domain as suffix
  • domain\user - User ID preceded by the domain

Configuring the browser

After you have configured the Active Directory and Kerberos authentication settings, you must make sure that the browser on a user's system is configured to use Kerberos authentication. Ensure that the browser is not on the same computer on which you have installed Remedy SSO server.

Configuring Internet Explorer

  1. Navigate to Tools > Internet Options > Advanced.
  2. On the Advanced tab and in the Security section, select Enable Integrated Windows Authentication (requires restart).
  3. On the Security tab, select Local Intranet.
  4. Click Custom Level.
  5. In the User Authentication/Logon section, select Automatic logon only in Intranet zone.
  6. Click OK.
  7. Click Sites and select all check boxes.
  8. Click Advanced and add the Remedy SSO service website to the local zone (the website might be already added). For example,
  9. Click Add.
  10. Click OK for all pop-ups.

Configuring Mozilla Firefox

  1. Enter the following URL: about:config.
  2. Click I'll be careful, I promise!
  3. Double-click the Preference Name: network.negotiate-auth.trusted-uris.
  4. Add the Fully Qualified Domain Name (FQDN) of the host, for example,
  5. Double-click the Preference Name:  network.automatic-ntlm-auth.trusted-uris.
  6. Add the fully qualified domain name (FQDN) of the host, for example,
  7. Click OK.

Related video

Click the image to view the video.

Related topics

Was this page helpful? Yes No Submitting... Thank you


  1. Mohamed Atta

    I have a question here, Does Safari browser support RSSO Kerberos Authentication? If yes, how to configure safari to use Kerberos Authentication?

    Thanks Atta

    May 23, 2018 06:59
  2. Guruprasad Balachandra

    Adding an SPN mapping for the service account steps mention above apears to suggest it needs to be executed on Active directory server in wich case it needs to be performed by "Active Directory Administrator" and not "Remedy SSO administrator". please clarify

    May 16, 2019 10:56
    1. Olga Kutetska


      Thank you for the question. Yes, you need Active Directory administrative permissions to configure Kerberos authentication for RSSO (in particular, when adding SPN). We will update the document to clarify this.

      May 17, 2019 07:33