FAQs: Using Cookies with the e–Library and Hyperion

The e–Library and Hyperion do not use any cookies by default. However, they can be configured to use cookies to help users log in or to maintain their current e–Library session.

Use of cookies is controlled through the WebCat/iBistro configuration files. If the /Unicorn/Webcat/Config/webconfig file has COOKIE_LOGIN and COOKIE_SESSION environment parameters defined as 0 instead of 1, then you can be sure that the e–Library will not set or retrieve any cookies whatsoever.

If COOKIE_LOGIN value is 1, then the user’s user ID, alt ID, and PIN are stored on his workstation as a cookie that only the e–Library server can access later to automatically log that user back in.

If COOKIE_SESSION value is 1, then the user’s current e–Library session number is stored as a cookie, which is used to let a user get into his current session if he exits out and then back into the e–Library. This setting is mainly used to make some Hyperion features more efficient.