Getting Server error - $(HttpStatus) after Submitting the Screen in User Portal
We Recently Upgrade the Pega 8.5.3 to 8.8 ,we are Facing an Issue in the UI as "Getting Server error - $(HttpStatus) after Submitting the Screen in User Portal".
ScreenShot is Mentioned Below.
***Edited by Moderator Marije to add Capability tags***
Pegasystems Inc.
IN
Hi @vinayJ40
Are you seeing SECU0019 error in PDC ?
Here some existing post reporting similar issue.
Pega Platform version 8.5 introduced this feature. When pyBlockUnregisteredRequests is enabled in development, the application development team can detect and respond to any problems with unauthorized or unregistered requests well ahead of application staging and production deadlines. In Pega Platform versions 8.5.6 and higher, 8.6.3 and higher, and 8.7 and higher, the when rule blocks unauthorized requests by default at production level 2 (Development/Test) or higher. In versions prior to 8.5.6, 8.6.3, and 8.7, the when rule blocks unauthorized requests by default at production level values of 4 (4 is Staging, 5 is Production) or higher. See Verifying requests when using custom controls for registration steps for the user request based on the various scenarios. As a security best practice, ensure that you properly enable pyBlockUnregisteredRequests to return a value of True to block unregistered requests.
Here links and docs on this feature
https://docs-previous.pega.com/security/87/verify-requests-application-layer
Hi @vinayJ40
Are you seeing SECU0019 error in PDC ?
Here some existing post reporting similar issue.
Pega Platform version 8.5 introduced this feature. When pyBlockUnregisteredRequests is enabled in development, the application development team can detect and respond to any problems with unauthorized or unregistered requests well ahead of application staging and production deadlines. In Pega Platform versions 8.5.6 and higher, 8.6.3 and higher, and 8.7 and higher, the when rule blocks unauthorized requests by default at production level 2 (Development/Test) or higher. In versions prior to 8.5.6, 8.6.3, and 8.7, the when rule blocks unauthorized requests by default at production level values of 4 (4 is Staging, 5 is Production) or higher. See Verifying requests when using custom controls for registration steps for the user request based on the various scenarios. As a security best practice, ensure that you properly enable pyBlockUnregisteredRequests to return a value of True to block unregistered requests.
Here links and docs on this feature
https://docs-previous.pega.com/security/87/verify-requests-application-layer
https://docs-previous.pega.com/security/87/verifying-requests-when-using-custom-controls