Unsupported content


This version of the product is in limited support. However, the documentation is available for your convenience. You will not be able to leave comments.

Configuring settings for Remedy SSO server

Review the following network, logging, and user session settings for Remedy SSO server, and configure them as required:

To set the cookie domain

The cookie domain controls the cookie visibility between servers within the same domain or different domains.

The default cookie domain value is the network (parent) domain of the computer on which the Remedy SSO server is installed. The default cookie domain specifies the most restrictive access.

You can set the specific domain name where the Remedy SSO server is installed, instead of the parent domain. For example, if your Remedy SSO server is on rsso.yourcompany.com, you can now set the cookie domain to rsso.yourcompany.com instead of just yourcompany.com.

For example, if your ITSM and BMC Digital Workplace applications are available on itsm.yourcompany.com and dwp.yourcompany.com and Remedy SSO is on sso.yourcompany.com, then the cookie domain must be set to sso.yourcompany.com.

  1. In the Remedy SSO Admin Console, click General > Basic.
  2. In the Cookie Domain field, enter the cookie domain value.


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

    Ensure that the value is correct because a wrong value can cause a redirection loop.

  3.  Click Save.

To set the cookie name

The cookie name is automatically created during the installation of Remedy SSO, and the name is shared between all applications that use Remedy SSO.

If you configure Remedy SSO across multiple staged environments within the same domain, you must specify a unique cookie name for each environment. For example, if you have four environments (DEV, QA, STAGING, and PRODUCTION), each group of applications within the same domain must have the environment's unique cookie name.

  1. In the Remedy SSO Admin Console, click General > Advanced.
  2. In the Cookie Name field, enter a unique value.

    The default cookie name is a timestamp value, which is generated when the Remedy SSO database is installed. 

  3. Click Save.

To secure the cookie

You might need to secure the cookie if all integrated applications run on HTTPS, and are accessed only through HTTPS. 

  1. In the Remedy SSO Admin Console, click General > Advanced.
  2. Select the Enable Secured Cookie check box.
  3. Click Save.

To set the service URL on the Remedy SSO server

The service URL provides information about the location of the Remedy SSO server, and the server uses the service URL to generate the token.

  1. In the Remedy SSO Admin Console, click General > Advanced.
  2. In the Service URL field, set the Remedy SSO service URL. 
  3. Click Save.

If you do not set the service URL on the Remedy SSO server, you can specify the server location in the rsso-agent.properties configuration file on the  Remedy SSO agent and the AREA plugin file

To configure the log level for the Remedy SSO server

  1. In the Remedy SSO Admin Console, click General > Basic.
  2. From the Server Log Level list, select a severity level for logging messages.


    The DEBUG level affects the Remedy SSO server performance.

  3. Click Save.

To configure the maximum session time for end users

  1. In the Remedy SSO Admin Console, click General > Basic.
  2. In the Max Session Time field, set the time after which the user session expires.
    When this value is selected, time constraints are automatically enforced. By default, 24 hours is set.


    The time that you set must be more than the time that is set for session token validation on the Remedy SSO agent.

  3. Click Save.

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