Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Cloe Walker (CloeW938)
IT Solution Service

IT Solution Service
SG
CloeW938 Member since 2018 227 posts
IT Solution Service
Posted: Jul 23, 2018
Last activity: Jul 31, 2018
Posted: 23 Jul 2018 11:16 EDT
Last activity: 31 Jul 2018 0:17 EDT
Closed
Solved

What are the differences between JSESSIONID cookie and Pega-RULES cookie?

Hi,

I understand that JSESSIONID is not Pega specific but general name of cookie that are created by App server or load balancer. Pega-RULES is on the other hand, a cookie that is created by Pega. So I am okay with who creates it but what are the actual differences? Which is the one that identifies the user uniquely? Also, I see some hash strings (requestor ID?) sometimes somewhere, but how are they related to these JSESSIONID or Pega-RULES?

Thanks,

***Edited by Moderator Marissa to update platform capability tags***

To see attachments, please log in.
System Administration

  • Smriti Singh

Accepted Solution

Posted: 6 years ago
Posted: 24 Jul 2018 8:41 EDT
Domenico Giffone (DomenicoGiffone)
PEGA
Senior Principal Software Engineer
Pegasystems Inc.
IT

Very good question that was addressed quite frequently in the past. Please find below some good explanation:

https://docs-previous.pega.com/how-process-commander-uses-http-cookies
https://collaborate.pega.com/question/how-set-cookies-how-does-prpc-handle-cookies

To recap JSESSIONID cookie is set by the Servlet Container and is is used for HTTP Session tracking and, in  load balancing, for session affinity.

On the other end Pega-RULES cookie is associated with the (authenticated or not) Browser Requestor and its value is the RequestorID

As in Pega each user session is identified uniquely by the RequestorID the Pega-RULES cookie is a a mean to identify a specific user session.

To see attachments, please log in.
Posted: 6 years ago
Posted: 24 Jul 2018 16:04 EDT
Chandrasekhar Gollamudi VN (chandrasekhar_g)
PEGA
Senior Manager, Technical Support - Runtime Engine and Search
Pegasystems Inc.
IN

Hi,

Main difference is below :

JsessionID is set by application server, not Pega7. It is used for load balancing / session affinity.

Pega associates browser calls with requestors via the PegaRULES cooke, which is the requestorID.

 

To see attachments, please log in.
  • Smriti Singh MALLESAPPA JAYARAMAPPA GARI NAVEEN

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice