Unregistered Request Encountered on Refreshing launched portal

User Experience
, , , , , , ,
1

After an upgrade from 8.4.1 to 8.4.4, we are observing that when we launch a portal from Dev studio and then try to refresh the portal, the response recieved is “Unregistered request encountered”

Query string on the URL:

?pyActivity=%40baseclass.pzProcessURLInWindow&pyPreActivity=Embed-PortalLayout.RedirectAndRun&ThreadName=OpenPortal_UserPortal&Location=pyActivity%3DData-Portal.ShowSelectedPortal%26portal%3DUserPortal%26Name%3D%20UserPortal%26pzSkinName%3D%26developer%3Dfalse%26ThreadName%3DOpenPortal_UserPortal%26launchPortal%3Dtrue&target=popup&portalThreadName=STANDARD&portalName=Developer&pzHarnessID=HID4AF326A00D75C089CF06FF9DC61C9E3C

On tracing we find that an OOTB functions that checks whether the URL is registered or not returns false and hence it shows this response rather than processing the request.

From the documentation I was not very clear on how we can register these type of URLS and how can we prevent this unregistered response and rather get the expected html response.

I guess this is probably a good security feature introduced but not very clear on how and where can we register URLs. Need help from experts on this

2

@AnkujJ44 hi Ankuj, did you got any details on how to register.

3

@AnkujJ44 Please try changing the value on “pyBlockUnregisteredRequests” when rule to ‘5’ .

4

@AnkujJ44

I don’t know if you’ve customised the portal you’re launching, but if it’s OOTB try scanning for missing hot fixes. After an update we also ran into the same kind of warnings and it was a pega known issue.

5

@AnkujJ44 the main documentation can be found here: Configuring the custom control by encrypting the URL in JavaScript

However, I think the known issue which @BasM7674 is referring to might be the error ‘Unregistered request encountered’ which occurred when a user would click refresh on Browser - it only impacted the patch upgrade, from 8.4.x to 8.4.4

This has been resolved by adding a pySecureFeatures check in step1 of pzProcessURLInWindow activity (which is listed in your error above). In the corrected Pega patches for pzProcessURLInWindow activity we are executing the activity in designer studio irrespective of activity is registered or not through secured features check.

Please update your environment to 8.4.5 where it was resolved as part of BUG-634766 (you can check in the Resolved Issues documentation).

The issue does not occur from 8.6 onwards as BAC is disabled for Developer Studio in 8.6.

.