I would like to configure a cookie domain for the Unblu application in such a way that an existing Unblu session can remain active when a visitor navigates to a sub-domain.
Unblu supports sub-domain switching. This means a session can remain active if there is a navigation to another sub-domain. This requires a definition of a cookie domain in the Unblu server configuration file (unblu.properties).
The following property should be used to define a cookie domain:
A cookie domain can be set in one of the following ways; depending on the requirement/use-case (valid from Unblu 3.5.x and all new versions):
If no sub-domain-switch is required: then no cookie domain needs to be defined. In this way Unblu uses the current context origin as the cookie domain. For example, consider the visitor is on https://www.example.com. In this case Unblu uses www.example.com as the cookie domain when creating cookies.
If a sub-domain-switch (only for one domain) is desired: it requires a cookie domain to be set as follows:
In this case Unblu will use .example.com as a cookie domain when creating cookies. As a result, a sub-domain switch is possible. This means if the visitor navigates to a sub-domain (let us say to subdomain1.example.com) and the Unblu snippet is present on that page, the Unblu session will remain active.
If a sub-domain-switch is required (for more than one domain): a cookie domain should be set as follows:
In this case Unblu will set the cookie domain to the second level domain of the current context origin. For example, consider the visitor is on https://www.example.com. In this case Unblu uses .example.com as the cookie domain. As a result, a sub-domain-switch is possible for multiple domains (but only for the current context origin domain).