Cookies are created to identify you when you visit a new website. The contents of a cookie are application-defined, and there are all sorts of ways to use them:
Session management. For example, cookies let websites recognize users and recall their individual login information and preferences
Personalization. You may view certain items or parts of a site, and cookies use this data to help build targeted ads that you might enjoy.
Tracking. Suggestions based on your previous researches.
Demodesk allows you to save your session cookies and leverage it during web demos. This helps you to automatically stay logged in on a website without having to insert your credentials over and over again.
You can enable cookies in your personal settings (Settings > Personal Profile > Meetings > Enable "Save session cookies" or click the button below):
However, sometimes it might not work. Here is a short list of some of the possible reasons why your effort failed:
Your website uses localStorage and thus specific to the protocol of that page. Therefore, data stored by a script on a site accessed with HTTP is put in a different localStorage object from the same site accessed with HTTPS.
The cookie is bound to the IP address, device fingerprint, or other non-cookie data that you didn't capture.
The original cookie contains an expiration after a specific time and it has passed.
The cookie is single-use, i.e. the server rotates the value with every request/response and invalidates any cookie value that has already been used.
The cookie was bound to a session that no longer exists on the server (potentially because you logged out).
The cookie is paired with a hidden element within the page (e.g a CSRF token) and you didn't capture or recreate that value.
The web server uses a rules engine to detect suspicious activity, and your spoofed cookie was presented out of sequence or at an unexpected time.