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

Secu0001 Alert is being logged Alert logs



Secu0001 alert is being logged in the alert logs extensively. Why is this alert being logged so often and how can we turn if off.

Error Messages

The following unexpected properties were received in an HTTP request for Thread TABTHREAD1: param.bAllowMissingProperties

Steps to Reproduce

We have an iFram in one of our assignments. Embedded that iFrame in another assignment. Looks like when that iFrame is brought up it throws this alert.

Root Cause

The root cause of this problem is a defect in customer application code/rules.  
The param.bAllowMissingProperties is being passed into the request including the "param."  


The explanation for this behavior is as follows:
SECU0001's are often called by systems that replay HTTP traffic. The alert is telling you that the post data and the harness don't match input field properly.  You will see a SECU0001 when you have additional properties that weren't expected in your post data. Get rid of the extra properties, SECU0001 goes away.

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