If your ITSM and BMC Helix Digital Workplace applications are available on itsm.yourcompany.com and dwp.yourcompany.com, and BMC Helix SSO is on sso.yourcompany.com, then the cookie domain must be set to sso.yourcompany.com.
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.
For more information, see Setting up tenants.
By default, the session timeout is set as 4 hours. When this value is selected, time constraints are automatically enforced.
From the Server Log Level list, select a severity level for logging messages.
The DEBUG level affects the BMC Helix SSO server performance.
If you configure BMC Helix 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 Cookie Name field, enter a unique value.
For end users, the secure cookie is disabled by default. To enable the secure cookie:
If this check box is selected, the end user cannot log in to BMC applications integrated with BMC Helix SSO without HTTPS.
To enable a cross site cookie for a browser, perform the following steps:
The service URL provides information about the location of the BMC Helix SSO server, and the BMC Helix SSO server uses the service URL to generate session tokens.
For administrators, the secure cookie is disabled by default. To enable the secure cookie:
If this check box is selected, the administrator cannot log in to the BMC Helix SSO Admin Console without HTTPS.