Forum Discussion
NimbostratusAPM domain cookie
We have multiple APM profiles all using the domain cookie ( domain.com) so single sign on works fluidly between different services. e.g webmail.domain.com and sharepoint.domain.com We also have a different BigIP appliance for test purposes, where the same domain cookie name is used (domain.com) for all our test services webmail-tst.domain.com (for example). This causes problems if people try to mix services between production and test in the same browser session e.g. webmail-tst.domain.com and sharepoint.domain.com as the cookie is obviously only valid for the device which issued it.
Am i correct in assuming that the domain cookie has to match the actual url domain or could i specify a different domain cookie name (e.g. domain-tst.com) so that they no longer clash?
2 Replies
Michael_JenkinsCirrostratus
Yes, I think your best bet would be to use a separate domain (i.e. domain-test.com) on the test box and just make sure that your other domains can use it as well (i.e. webmail.domain-test.com). The domain-test.com cookie should get sent with all the sub domains as well, and not clash with the domain.com cookie. The difficulty here might just be getting your applications (like SharePoint) listening on the test domain as well.
Seth_CooperEmployee
The best solution would be to change the name of the MRHSession cookie and we currently have an RFE ID to make this possible. Please open a case with support and have your company linked to RFEID 473352. This will get attention to the feature and hopefully get it added quicker.
Since it isn't possible today to change the name of the cookie you will need to change you domain as Michael suggests.
Seth
