Create a specific subdomain on default installation to restrict visibility of SSO cookie
Until now, we use a wide domain (example.com) as default value, which is not a good practice, as the SSO cookie is then visible for all applications on this domain.
We should instead configure a subdomain (sso.example.com) with portal and manager inside it (auth.sso.example.com and manager.sso.example.com).