Skip to main content

Jive cookies

Here you can find the list of cookies which Jive uses in communities.

Note: Except where noted, none of the following cookies contains user-identifiable information. This behavior meets European Union privacy laws.

Jive sets the following cookies:

anonymous : Used only by the Gamification module. Tracks if the user is authenticated or not.

  • Possible values: true or false
  • Expiration: one year
  • Encryption: none
  • Example: anonymous="false"

BIGipServer : Cookies prefixed with BIGipServer help to efficiently route internal traffic, and contain encoded addresses of internal Jive servers. These addresses are strictly internal, and cannot be used to connect to internal servers from the Internet. Altering the values of the cookie does not have any effect. For more information about these cookies, see the Overview of BIG-IP persistence cookie encoding article on the F5 Support site at https://support.f5.com/kb/en-us/solutions/public/6000/900/sol6917.html.

clickedFolder : This cookie is used in the Admin Console to persist the open or closed status of the current folder as used in various tree-view portions of the Admin Console.

  • Possible values: String, true, or false
  • Expiration: At session end
  • Encryption: None
  • Example: clickedFolder="true"

highlightedTreeviewLink : This cookie is used in the Admin Console to persist the current folder as used in various tree-view portions of the Admin Console.

  • Possible values: Integer, the DOM ID of the clicked folder
  • Expiration: At session end
  • Encryption: None
  • Example: highlightedTreeviewLink="23"

jive.cookie.consent.accepted : This cookie is used to check if the cookie consent warning is already accepted.

  • Possible values: true or false
  • Expiration: 1 year
  • Encryption: None
  • Example: jive.cookie.consent.accepted="true"

jive.oauth.token : This cookie contains Authentication Token value.

  • Possible values: String
  • Expiration: At session end
  • Encryption: None

jive.user.lastvisited : This cookie is used to store the last time the user visited the site.

  • Possible values: UNIX timestamp
  • Expiration: 30 days
  • Encryption: None
  • Example: CookieUtils.setCookie(request, response, "jive.user.lastvisited", Long.toString(now));

jive.embeddedResponsive : This cookie is used to control view related logic.

  • Possible values: true or false
  • Expiration: At session end
  • Encryption: None
  • Example: jive.embeddedResponsive="true"

jive.loginEventFired : This cookie is used when a registered user logs in.

  • Possible values: true or false
  • Expiration: At session end
  • Encryption: None
  • Example: jive.loginEventFired="true"

jive-cookie : This cookie is used in the Admin Console to temporarily persist an encrypted username and password when creating a bridge between two sites. The information in the cookie is first encrypted with AES 256 encryption, and then Base64 encoded.

  • Possible values: String, Base64 encoded, encrypted username and password of the remote site
  • Expiration: At session end
  • Encryption: Yes
  • Example: jive-cookie="YWFyb246MTMxNTU4MjUzNTI3MDoyZDUyODNmZjhhNjExZTdlMTcyMGZhYjVhNWNkNjI0Yg"

jiveRegularLoginUserCookie : This cookie is used to auto-redirect the login screen to the built-in authentication page (if the value exists and is set).

  • Possible values: true
  • Expiration: One month
  • Encryption: None

jive.login.ts : This cookie stores the time stamp of the user last login.

  • Possible values: Unix time in ms
  • Expiration: At session end
  • Encryption: None
  • Example: 1387387736841

jive.saml.passive.tried : This cookie is used to mark when SAML passive authentication has already been attempted.

  • Possible values: true
  • Expiration: 3600 seconds (one hour)
  • Encryption: None
  • Example: jive.saml.passive.tried="true"

jive.security.context : This cookie is the authentication context for the user.

  • Possible values: The user's encrypted security context
  • Expiration: 30 minutes unless refreshed. Same as the standard servlet container session timeout
  • Encryption: AES 256
  • Example: jive.security.context="SdRw2i/HXoh1+LwTBLFy3Q==.MzA3OQ=="

jive.server.info : This cookie is used on the front-end in combination with Content Distribution Networks (CDN) to associate the user with a specific server (also known as session affinity).

  • Possible values: String, a combination of the serverName, serverPort, contextPath, localName, localPort, and localAddr
  • Expiration: At session end
  • Encryption: None
  • Example: jive.server.info="serverName=community.example.com:serverPort=443:contextPath= :localName=localhost.localdomain:localPort=9001:localAddr=127.0.0.1"

jiveSSOLoginUserCookie : This cookie is used to auto-redirect the SSO screen to the built-in authentication page (if the value exists and is set).

  • Possible values: true
  • Expiration: One month
  • Encryption: None

jiveTimeZoneID : This cookie is used on the front-end for guest and anonymous users who choose a timezone setting.

  • Possible values: String, timezone ID
  • Expiration: 30 days
  • Example: jiveTimeZoneID="234"

jive.user.loggedin : This cookie is used on the front-end in combination with Content Distribution Networks (CDN) to denote the status of the current request.

  • Possible values: String, true if the current request originates from a browser where the user is logged in
  • Expiration: At session end
  • Encryption: None
  • Example: jive.user.loggedin="true"

jive_wysiwygtext_height : This cookie is used on the front-end to persist the height of the editor window across sessions.

  • Possible values: Integer, the height in pixels of the editor after the user chooses to expand the editor window
  • Expiration: 1 year
  • Example: jive_wysiwygtext_height="500"

JSESSIONID : This cookie is used on the front-end and the Admin Console to identify a session. It is part of the Java Servlet specification, as described in http://www.oracle.com/technetwork/java/javaee/servlet/index.html.

  • Possible values: String, the unique token generated by Apache Tomcat
  • Expiration: At session end
  • Encryption: None
  • Example: JSESSIONID="1315409220832msB9E3A98AA1F2005E61FA975963FA4D12.node01"

linkedin_oauth_ : This cookie is used to communicate and authenticate with LinkedIn.

place_info : This cookie is used to temporarily store the tile configuration information when a user is configuring a tile that integrates with a third-party system, such as Google Docs. After the user clicks Save in the place template editing interface, the cookie is destroyed.

  • Expiration: After place template changes are saved
  • Encryption: None
  • Example: place_info="placetype%3A700%26placeid%3A5758"

skin.palette.preview : This cookie is used to preview the site with an unpublished template.

  • Possible values: ID (long value) of the template
  • Expiration: 30 days
  • Encryption: None
  • Example: skin.palette.preview="1001"

SPRING_SECURITY_REMEMBER_ME_COOKIE : This cookie is used on the front-end as part of the security authentication process to denote whether or not the user wants to have their credentials persist across sessions. It is part of the Spring Security specification, as described on this page.

  • Possible values: String, the Base64 encoded username and expiration time combined with an MD5 hex hash of the username, password, expiration time, and private key
  • Expiration: Defaults to 14 days
  • Encryption: None. This is an MD5 hex hash
  • Example: SPRING_SECURITY_REMEMBER_ME_COOKIE="YWFyb246MTMxNTU4MjUzNTI3MDoyZDUyODNmZjhhNjExZTdlMTcyMGZhYjVhNWNkNjI0Yg"
Related

Cookies in Jive communities