Support Article
URL's are not encrypted
SA-38096
Summary
The user reported that even after setting the following DSS, the URL's are neither encrypted nor obfuscated.
- prconfig/initialization/urlencryption/default - true
- prconfig/initialization/submitobfuscatedurl/default - optional
And moreover, after the above changes the portals except developement portal seems to not work.
Error Messages
'length' is null or not an object
pega_ui_harness_deferred_1232858027!!.js
Steps to Reproduce
Change the following DSS file
- prconfig/initialization/urlencryption/default.
- prconfig/initialization/submitobfuscatedurl/default.
- Then open the portal.
- Click on any module.
Root Cause
The root cause of this problem is defect/misconfiguration in the PRPC operating environment. URLs generated by custom Javascript were not passed through a SafeURL encoder and thus encountered errors after being encrypted.
Resolution
Perform the following local-change:
When generating URLs in custom javascript, rather than using this implementation:
var oTempURL = pxReqURI+"?pyActivity=ORG-FW-Application-Work.Document&DocName="+docname;
use this implementation:
var oTempURL = new SafeURL(ORG-FW-Application-Work.Document)
oTempURL.put("DocName",docname);
The safeURL function is necessary to create URLs in a way that the URL obfuscation algorithms can parse.
Published May 17, 2017 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.