Setting up Kerberos authentication in Remedy SSO
Before you begin
You must have installed and configured the Remedy SSO to work with the Presentation Server and its component products. For details, see Planning to deploy Remedy SSO and Installing Remedy Single Sign-On.
You must have created an equivalent local user(and its associated local usergroup) for every Kerberos user that needs to log into the Presentation Server. This is required because the Remedy SSO server cannot obtain usergroup information from the Kerberos identity provider for the successfully logged in Kerberos user. Therefore, you need to create an equivalent local user with the exact name as the Kerberos user and associate that local user with the desired local usergroup. For details on creating local users and usergroups in Remedy SSO using the import utility, perform the Migrating internal user data from Atrium SSO to Remedy SSO procedure.
- You must have added a non-default tenant (realm) in addition to the default * tenant (realm). Configuring-tenants-for-the-Presentation-Server-in-Remedy-SSO.
You must have configured a multi-tenant environment by enabling the msp parameter. For enabling multi-tenancy, see To enable multi-tenancy in Presentation Server.
- Create a service account in Active Directory and configure the Service Principal Name (SPN)
- Obtain the following information:
- Host name of the Key Distribution Center (KDC)
- 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
Configuring Active Directory
To configure Active Directory, perform the following steps:Creating a service account in Active Directory
Adding an SPN mapping for the service account
Before you begin
To add an SPN mapping
To add an SPN mapping, run the setspn command on one of the directories in the Active Directory machine.
For example,(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
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.
For example,
Configuring Kerberos authentication in Remedy SSO for the TrueSight Presentation Server
Perform the following procedures to configure the Kerberos authentication for TrueSight Presentation Server:
- To configure the Kerberos authentication in Remedy SSO for the TrueSight Presentation Server
- To create or edit an authorization profile with Kerberos users in the Presentation Server
To configure the Kerberos authentication in Remedy SSO for the TrueSight Presentation Server
- Log in to the Remedy SSO Admin console.
- In the left navigation panel of the Add Realm or Edit Realm page, click Authentication.
- In the Authentication Type field, click KERBEROS.
Enter the Kerberos details. For more information on parameters, see Kerberos authentication parameters.
- Click Test to verify the settings.
- Click Save.
- In the left navigation panel of the Add Realm or Edit Realm page, click Authentication.
- In the Authentication Type field, click Kerberos and click Enable Chaining Mode.
- Click Add Authentication.
- In the Authentication Type field, click LOCAL.
- Enter the LOCAL details. For more information on parameters, see LOCAL authentication parameters.
- Create users and user groups for the LOCAL authentication.
The users in LOCAL should be exactly same as the users in Kerberos identity provider.
Alternatively, the users can also be created using import script under the migration utility. - Associate users to the user groups.
- Click Save.
To create or edit an authorization profile with Kerberos users in the Presentation Server
- Log in to the TrueSight console as a Super Admin.
- Navigate to Administration>Authorization Profiles.
- Create a new authorization profile or edit an existing authorization profile to associate the user groups.
Select a tenant other than the * (asterisk) tenant that you configured in Remedy Single Sign-On for Kerberos users and select Edit under User Groups.
- Click Add and select the Kerberos user group from the list of user groups.
- Select the required roles from the list roles.
- (Optional) Select the required objects from the list of object.
- Select OK and then Save.
- Select Yes to confirm changes to the authorization profile.
- Log out of the TrueSight console.
- Configure the browsers for Kerberos authentication to work.
- Log in to the TrueSight console as a Kerberos user.
A two-step authentication screen is displayed. - Type the Kerberos realm Application Domain name and click Submit.
The Kerberos login screen is displayed. - Type the Kerberos login credentials and click Login.
The TrueSight console is displayed.
Configuring the browsers
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
- Navigate to Tools > Internet Options > Advanced.
- On the Advanced tab and in the Security section, select Enable Integrated Windows Authentication (requires restart).
- On the Security tab, select Local Intranet.
- Click Custom Level.
- In the User Authentication/Logon section, select Automatic logon only in Intranet zone.
- Click OK.
- Click Sites and select all check boxes.
- Click Advanced and add the Remedy SSO service website to the local zone (the website might be already added). For example, sample.bmc.com.
- Click Add.
- Click OK for all pop-ups.
Configuring Mozilla Firefox
- Enter the following URL: about:config.
- Click I'll be careful, I promise!
- Double-click the Preference Name: network.negotiate-auth.trusted-uris.
- Add the Fully Qualified Domain Name (FQDN) of the host, for example, sample.bmc.com.
- Double-click the Preference Name: network.automatic-ntlm-auth.trusted-uris.
- Add the fully qualified domain name (FQDN) of the host, for example, sample.bmc.com.
- Click OK.