|
AWSALB
|
1
|
AWS sticky session cookie required for load balancer routing. See this document for further information.
|
Session
|
Sticky session won't work and some functionality will break.
|
| AWSALBCORS |
1
|
For continued stickiness support with CORS use cases after the Chromium update, we are creating additional stickiness cookies for each of these duration-based stickiness features named AWSALBCORS (ALB). See https://forums.aws.amazon.com/ann.jspa?annID=7413 for further information.
|
Session
|
|
|
_ga
|
2
|
Distinguishes users using a unique ID. It is used by Google Analytics to calculate visitor, session, and campaign data. By default, the configuration setting that sets this cookie is disabled. File a Support ticket to request enablement.
|
2 years (persistent)
|
Visitor and session data will not be tracked and will not be available to Google Analytics
|
|
!lithiumSSO:{client_id}
|
1
|
Used for passing authentication information to Khoros
|
session
|
SSO will not be functional for the user
|
|
LiSESSIONID
|
1
|
Session management
|
session
|
User cannot log in, and is treated as an anonymous user
|
|
lia.anon.{setting or config name}
|
3
|
Stores community-wide configurations and settings for anonymous users
|
1 year (persistent)
|
Community behavior will follow defaults and any UI convenience changes made by the user will be ignored.
|
|
liSdkOptions:{communityId}
|
3 |
Dropped when a Studio user navigates to Studio > Advanced > SDK and clicks Submit after checking the View as anonymous checkbox.
The cookie allows developers to sign out of the community but still have it find the URL to use for rendering a skin that is hosted via the Community Plugin SDK.
This cookie is used only on stage sites.
|
1 month or when the View as anonymous checkbox is unselected |
The community will serve the URL for the skin set on the stage site instead of the URL to the locally hosted skin (so local SASS development will not work when the user is signed out) |
|
lithium.anonymous.
usersetting.{setting name}
|
3
|
Remembers user preferences
|
1 year (persistent)
|
The community will not remember the user’s setting preferences
|
|
lithium.anonymous.
usersetting.profile.
language
|
3
|
Remembers language preferences
|
1 year (persistent)
|
The community will not remember the user’s language preferences. The language will default to the native language defined for the community.
|
|
lithiumLogin:{community id}
|
3
|
Keeps users logged in when they make a request after their session has expired. It is triggered when a user checks Save login name and password. The cookie is encrypted and includes a unique user secure ID in the database.
|
30 days (persistent)
|
The "auto login" and "remember me" features will not work
|
|
LithiumNotifications
|
3
|
Temporarily stores Realtime Notification messages (Toast messages)
|
session
|
Realtime notification toasts may not appear (pop-up) after a page transition.
|
|
LithiumUserInfo
|
1
|
Session management
|
session
|
The user will not be able to view secure pages and will be redirected to the login page
|
|
LithiumUserSecure
|
1 |
Secure Session management |
session |
The user will not be able to view secure pages and will be redirected to the login page. |
|
LithiumVisitor
|
4
|
Replaces VISITOR_BEACON. Khoros currently uses both for backward compatibility. This cookie computes billing visits, registered billing visits, visits, registered visits, and unique visitors metrics. The cookie is encrypted and stores when it was first issued, when it was last seen by Khoros, an unique visitor ID (which is unique per visitor’s browser).
|
Configurable (Default = 10 years)
Note: To change the default value, contact Khoros Support.
|
Visits and unique visitors metrics will not be accurate. There will be a new billable visit on each new request. Customers on billing visits model will be affected.
|
|
P{poll_id}U{user_id}R{reset_count}
|
3
|
Tracks when a user has voted in a poll and tracks the answer value. The cookie is used to prevent a user from voting multiple times in a single poll. The cookie is only placed if Use cookies to prevent multiple votes is enabled in Community Admin.
|
1,000000+ days
(persistent)
|
If the user is an anonymous user, the user will be able to vote multiple times when the cookie is cleared. If the user is logged in, votes, and then clears the cookie, they are not allowed to revote.
|
|
PushyAuthToken
|
1
|
Authenticates the user for a session with Realtime Notifications service (Pushy)
|
Manually cleared when the user logs out or when their session expires due to inactivity
|
WebSocket connections to the Realtime Notification service will fail with a 403 Forbidden error and the user will not see realtime notifications.
|
|
VISITOR_BEACON
|
4 |
Computes billing visits, registered billing visits, visits, registered visits, and unique visitors metrics. The cookie is encrypted and stores, when it was first issued, when it was last seen by Khoros, the user ID, and its own unique ID.
|
Configurable (Default = 10 years)
Note: To change the
default value, contact Khoros Support.
|
Visits and unique visitors metrics will not be accurate. There will be a new billable visit on each new request. Customers on billing visits model will be affected.
|
|
VISITORID
|
1
|
Distinguishes between human and bot traffic
|
3 years (session)
|
Defeats the bot detection mechanism. (May see increased spam on the community.)
|
|
ValueSurveyParticipation
|
3
|
Stores a timestamp storing the creation time of this cookie, which is used in value survey trigger logic.
|
Default is 90 days. Configurable in Community Admin
|
The user will get multiple prompts to take a survey
|
|
ValueSurveyVisitorCount
|
3
|
Stores the survey visit count of the user, which is used in logic that determines when a survey is triggered. This cookie is used in conjunction with the ValueSurveyParticipation cookie. When the ValueSurveyParticiation is set, the count for ValueSurveyVisitorCount cookie is reset to 0.
|
Expires when the ValueSurveyParticipation cookie is either set or expires
|
The user will not be prompted to take a survey until the count defined in the Delay before prompting user with survey field in Community Admin > Features > Value Surveys > Settings is met.
|
