To set the cookie domain
The cookie domain controls the cookie visibility between servers within the same domain or different domains.
By default, the parent domain of a computer on which the Remedy SSO server is installed is set as the cookie domain value. The default cookie domain provides the most restrictive access to applications protected by Remedy SSO.
You can set a child domain name of a server where Remedy SSO is installed as the cookie domain value. For example, if your Remedy SSO server is on rsso.yourcompany.com, you can set the cookie domain to rsso.yourcompany.com instead of just yourcompany.com.
However, 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.
- In the Remedy SSO Admin Console, click General > Basic.
In the Cookie Domain field, enter the cookie domain value.
Note
The cookie domain value must contain a dot (".").
Ensure that the value is correct because a wrong value can cause a redirection loop.
- 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.
- In the Remedy SSO Admin Console, click General > Advanced.
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.
Click Save.
