Skip to main content (Press Enter).
Skip auxiliary navigation (Press Enter).
Code of Conduct
Skip main navigation (Press Enter).
on this day
between these dates
HL Community Managers
Higher Logic Staff Directory
Meet Your Product Advisory Council
Higher Logic Super Forum
SF 2015 Winners
SNAP! Product Training
Higher Logic Academy
Post a Message
Share a Resource
Join a Community
Documentation & Support
SNAP! Product Training Archives
Client Example/Go-to-Market Library
Resources for New Admins
CSS Knowledge Bank
Aggressive Cookie Strategy
For most of us, we have a single sign-on (SSO) solution in place to enable our visitors/members to access pages and functionality across all of our various applications (content management, connected community, ams e-commerce , etc...). Cookies are the glue that hold this single sign-on experience together. A "cookie" is dropped by your main authentication process, and within this "cookie" is the information needed by your other applications when you hand a visitor/member over from one application to the other.
Most "cookies" have relatively short life spans (just like in real life). It is common for "cookies" to expire after 20 minutes. An aggressive cookie strategy, therefore, is simply choosing to increase the lifespan of a "cookie" to an hour, a day, a week, a year or for a very, very long time. The benefit to this approach is that as long as a visitor/member comes back to your site using the same machine and the same browser, their "cookie" will be recognized and they will not be asked to log in.
Obviously, an aggressive cookie strategy emphasizes member convenience over security (although the overall security risk is minimal), so you should never implement it unless you have thought thru the trade-offs.
Dec 08, 2011
Last Updated By:
Aug 03, 2018
No Related Resource entered.
Higher Logic | 1600 Wilson Blvd, Suite 400, Arlington, VA 22209 | email@example.com | (202) 360-4402
Powered by Higher Logic
Add a tag
User Tags may not contain the following characters: @ # $ & :