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

ACCESS_OPEN - PRSecurityException

SA-33025

Summary



User noticed that "Access_Open" error appears when case is run with following configuration:

The mainflow contains atleast one subflow and one assignment; subflow contains many assignments.
or when the Perform Harness contains pxDisplayStages section.


Error Messages



2016-10-03 16:07:41,911 [ WebContainer : 4] [TABTHREAD0] [ Application] (ega_procom_pegaprocomutilities) ERROR 127.0.0.1|localhost Operator-Id - ACCESS_OPEN exception for
com.pega.pegarules.pub.context.PRSecurityException: ClassName on which access is requested is not specified
at com.pega.pegarules.session.internal.authorization.access.AccessEvaluator.haveAccess(AccessEvaluator.java:171)
at com.pega.pegarules.session.internal.authorization.Authorization.haveAccess(Authorization.java:1812)

<...>



Steps to Reproduce



1) Create a flow in which a Assignment and a sub-process exists.
2) Subprocess has multiple assignment shapes.
3) In perform Harness, include pxDisplayStages section.
4) Include the same section pxDisplayStages in Flow Action of a section.
5) After running the flow in the case, find the exception logged in PEGA_RULES logs.


Root Cause



Issue in the pzStageProcessLink control where Pega internally does security check even when assignment is not there.

This causes the Access_Open error.


Resolution



Apply HFix-31379.

Suggest Edit

Published June 16, 2017 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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