Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Session Identifier Not Updated



Session Identifier Not Updated 

Error Messages


Steps to Reproduce

Run AppScan Report

Root Cause

The root cause of this problem is a defect in Pegasystems’ code/rules. 

It is possible to steal or manipulate customer session and cookies, which might be used to impersonate a legitimate user, 
allowing the hacker to view or alter user records, and to perform transactions as that user


This issue is resolved by hotfix item
Added support for HttpOnly. As the HFix contains a change to status.jsp

with new portable encryption spec enabled in 5.5 GA and up, the base64-encoded string used for a pre-authentication cookie is now slightly longer than 70 characters, which caused the base64util class to add a line break near the end.  Cookies with line breaks violate the http spec because it ruins header parsing.
Added below parameter to prconfgi.xml
<env name="authentication/UsePreAuthenticationCookie" value="true"/>


Published January 31, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

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

Pega Community 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
Contact us