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

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

Configuring general settings for Remedy SSO server

After the installation of Remedy Single Sign-On (Remedy SSO), review and update the general configuration settings. If you want, you can export the configuration settings to back them up. Use the import option to restore the configuration settings, if needed.

In the general configurations, you can also set some SAML authentication settings. For example, including a certificate for signing a SAML request. You can configure Remedy SSO to decrypt the encrypted assertions in SAML responses. For more information about creating the signing certificate and encryption key for SAML assertions, refer Setting SP signing certificate for SAML authentication.

To update the general configuration settings

  1. Log in to the Remedy SSO Admin Console as an administrator.
  2. Click General.
  3. On the Basic tab, enter the basic server details.


    Cookie Domain

    The value that controls the cookie visibility between servers within the domain. The default cookie domain value is the network domain of the computer on which you are installing the Remedy SSO server. The default cookie domain specifies the most restrictive access.

    The cookie domain value must be the same for all integrated applications and Remedy SSO server.

    Note: The cookie domain value must contain a dot (".").

    For example, in case your ITSM and BMC Digital Workplace applications are available on and and Remedy SSO is on, then the cookie domain must be set to Ensure that the value is correct because a wrong value can cause a redirection loop.

    Installing Remedy SSO on another domain like your company.internal and setting the cookie domain to or your company.internal causes a redirection loop as the cookie cannot be set across different domains.

    Session Settings

    Max Session Time

    The time after which the user session expires. When this value is selected, time constraints are automatically enforced.

    The default value is 24 hours.

    Ensure that the maximum session time is more than the time that you configure for session token validation on an agent.

    Max Admin Session Time

    The time after which the admin session expires. When this value is selected, time constraints are automatically enforced. The default is 1 hour.

    The minimum value is 1 minute and the maximum value is 1 year.

    Admin Lockout Threshold

    The number of incorrect password attempts by an RSSO administrator account before the account gets locked out. 

    In version 18.08 and above, If the administrator enters an incorrect password, you can set the value in this field to make sure that after those many attempts, the administrator account gets locked out.

    The default value is 0, which indicates that the account lockout functionality is disabled.


    Server Log Level

    The level or severity of logging messages.

    Using the DEBUG level affects the server performance.

  4. On the Advanced tab, enter the following advanced details.


    Cookie Name

    The cookie name is automatically created at installation and is based on the timestamp. The timestamp is the time of creation of the database during Remedy SSO installation.

    Enable Secured Cookie

    The option to enable secured cookie. If this option is selected then all applications must also run on HTTPS and the application servers must be accessed through https only. Otherwise, it causes a redirection loop.

    Back Channel
    Service URLRemedy SSO generates a token and inserts this URL into the token to provide information about the location of the Remedy SSO server. This is an optional configuration as Remedy SSO server location can also be specified in the configuration files of Remedy SSO Agent and AREA plugin.
    SAML Service Provider (Optional) Enter these details only if you are configuring Remedy SSO for SAML authentication.
    SP Entity IDThe entity ID of the service provider (SP). You can specify any value for SP Entity ID, for example rsso_sp_hostname. Remedy SSO server name is used as SP identifier in Relying Party Trust configured on IdP side.
    External URLThe external URL of the service provider, that is, the URL for Remedy SSO server.  Note: The URL must be HTTPS only.
    Keystore File

    The keystore file path on the Remedy SSO server file system that includes the keystore file name. The keystore file contains all the required certificates. If you are using PKCS12 keystores file, the file extension must be .p12.

    If the keystore file is available in the tomcat/rsso/webapp/WEB-INF/classes folder, the value of this field can be the name of the keystore file, where tomcat is the Tomcat path. Otherwise, use the absolute file path.

    Keystore PasswordThe keystore file password. The keypair and keystore password must be the same.

    Signing Key Alias

    The alias name of the signing key in the keystore file.
    Encryption Key Alias
    The alias name of the encryption key used to decrypt the SAML assertions from the identity provider. The metadata of this encryption key is imported into the IdP.

    For information related to decrypting SAML assertions, see Security planning.

  5. On the Admin Authentication tab, click Add Authentication to configure the authentication type for administrators.

    Authentication Type
    The types of authentication for administrators.
    • Internal—Select this option to authenticate internal administrators. You can specify Internal authentication type only once. To add an internal administrator, see Setting up Remedy SSO administrator accounts.
    • LDAP—Select this option to authenticate external administrators and enter the details given following rows for getting administrators from the LDAP server. You can define LDAP authentication multiple times for authentication chaining.
    Server Host

    Host name of the LDAP server. You can specify more than one LDAP servers by providing a comma separated list of servers. If the first server is unavailable, the Remedy SSO server switches to the second one and so on.

    Server PortPort number for the LDAP server, such as 389.
    Bind DN

    The distinguished name (DN) of a bind LDAP user, such as CN=Administrator,CN=Users,DC=example,DC=com.

    This user must have privileges to search the directory.

    Bind Password

    Enter the password for bind LDAP user.

    Users Base DN

    Enter the starting location within the LDAP directory for performing user searches. For example, CN=Users,DC=example,DC=com.

    User Search Filter

    Enter the LDAP query to search for the user to be authenticated who has rights to use the admin resources in Remedy SSO.

    The user login ID is specified by $ADMIN$ keyword. For example - (&(objectCategory=user)(sAMAccountName=$ADMIN$)(memberof=CN=RSSOAdmin,OU=Users,DC=example,DC=com)).

    Identity Attribute

    Enter the LDAP attribute to be used as the login ID of the administrator. For example, sAMAccountName.

  6. Click Add to chain to add the admin authentication to the authentication chain.
  7. (Optional) Click arrow up or arrow down buttons to move the added authentication to a desired place in the authentication chain.
  8. Click Save.

Related videos

Click the image to view the video.

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