Forum Discussion
JP88730K_296639
Nimbostratus
NimbostratusAPM Session Visibility across VIPs
What is the best way to establish session visibility across multiple APM sessions without a SSO configuration or a persistent cookie? My site hosts projects which have multiple virtual servers. We us...
The browser must simply include the cookie in the request to be associated with the session. RFC 6265 defines exactly how this works, if you aren't familiar with it. The wikipedia article on HTTP cookies is also very good.
Customers usually choose one of the following options to share the cookie across multiple vips/hostnames:
-
Set the cookie domain to be wide like ".company.com" so that the cookie will be transmitted to *.company.com.
-
Use APM's multi-domain mode so that when APM gets a request without a cookie, it will "check with" the domain set as the primary-authentication URI to see if it's been set. This happens by using some 302 redirects between the hostanmes/vips.
For either of these options, make sure the session scope is set appropriately.
-
A way to achieve this with out-of-the-box behavior would be to have payroll1.company.com and payroll2.company.com use the same access policy, and sales.company2.com should use a separate access profile.
When a profile's SSO setting is in "Single Domain" mode, if you set the domain cookie to "company.com", then as long as the users for each site connect to other VIPs with the same policy with in their session timeout period, they should not go through the login process again. You can narrow this down to particular sites, and not domains, using the "Multiple Domains" setting.