PRSecurityException: Security violation attempting to access requestor

General
, , , ,
1

2023-10-25 13:50:04,383 [sse-nio-8402-exec-50] [ STANDARD] (pega.TRACE.requestor_lifecycle) DEBUG
m|12.19.89.221 - Attempt passivation blocking is succesfull. RequestorID: HJ7I8FFCRF0QQUD6LRXUTNN6ZT3YS0A72A, Blocker counter: 2, Main requestor ID: null
2023-10-25 13:50:04,383 [sse-nio-8402-exec-50] [ STANDARD] (pega.TRACE.requestor_lifecycle) DEBUG IDID.ABCDE.com|12.19.89.221 - Unblock requestor passivation. RequestorID: HJ7I8FFCRF0QQUD6LRXUTNN6ZT3YS0A72A, Blocker counter: 0, Main requestor ID:
2023-10-25 13:50:04,384 [sse-nio-8402-exec-50] [ STANDARD] (ineinterface.service.EngineAPI) WARN IDIDI.ABCDo.com|12.19.89.221 - Request Information is –
RequestURL = For Sale Domain: ib.com
Query String = pzPrimaryPageName=CTIPhone&AJAXTrackID=1&pzTransactionId=9be9a88370e1059364c41ea027df43cb
Requestor Id = HJ7I8FFCRF0QQUD6LRXUTNN6ZT3YS0A72A
Remote Address = 12.19.89.221
Referrer =null
2023-10-25 13:50:04,384 [sse-nio-8402-exec-50] [ STANDARD] (ngineinterface.service.HttpAPI) ERROR uiuj.hyxxii.com|12.19.89.221 - Exception occured:
com.pega.pegarules.pub.context.PRSecurityException: Security violation attempting to access requestor
at com.pega.pegarules.session.internal.engineinterface.service.HttpAPI.findRequestorInternal(HttpAPI.java:1734) ~[prprivate-session.jar:?]
at com.pega.pegarules.session.internal.engineinterface.service.HttpAPI.findRequestor(HttpAPI.java:1584) ~[prprivate-session.jar:?]
at com.pega.pegarules.session.external.engineinterface.service.EngineAPI.processRequest(EngineAPI.java:372) ~[prenginext.jar:?]
at com.pega.pegarules.session.internal.engineinterface.service.HttpAPI.invoke(HttpAPI.java:937) ~[prprivate-session.jar:?]
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._invokeEngine_privact(EngineImpl.java:338) ~[prprivate-session.jar:?]
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl$4.run(EngineImpl.java:287) ~[prprivate-session.jar:?]
at java.security.AccessController.doPrivileged(Native Method) ~[?:?]
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.invokeEngine(EngineImpl.java:284) ~[prprivate-session.jar:?]
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.invokeEngine(EngineImpl.java:259) ~[prprivate-session.jar:?]
at com.pega.pegarules.priv.context.JNDIEnvironment.invokeEngineInner(JNDIEnvironment.java:281) ~[prpublic.jar:?]
at com.pega.pegarules.priv.context.JNDIEnvironment.invokeEngine(JNDIEnvironment.java:226) ~[prpublic.jar:?]
at com.pega.pegarules.web.impl.WebStandardImpl.invokeEngine(WebStandardImpl.java:853) ~[prwebj2ee.jar:?]
at com.pega.pegarules.web.impl.WebStandardImpl.makeEtierRequest(WebStandardImpl.java:813) ~[prwebj2ee.jar:?]
at com.pega.pegarules.web.impl.WebStandardImpl.doPostInner(WebStandardImpl.java:435) ~[prwebj2ee.jar:?]
at jdk.internal.reflect.GeneratedMethodAccessor230.invoke(Unknown Source) ~[?:?]

PRSecurityException.png
PRSecurityException.png1896×799 92.3 KB

2

@RajaKullaiahD16662217 Likely this issue occurs when there is a long gap between login activity and new activity on the screen. See documentation.

Kindly review the Authentication Service rule for timeout settings and the timeoutactivity in the authentication service.

Review also Access groups of the users experiencing issues and modify timeout - do users observe if the credentials pop up is displayed.

Next Steps/Actions:

  1. Test workaround to configure timeout in access groups and create timeout activity such that the session is invalidated and routed back to the login URL

  2. Test workaround for few access groups and observed for a pattern when issue occurs.

Then if required log a support incident via the MSP. Let us know the INC ticket id if you decide to contact our GCS team.

*** Please hit the Accept Solution on this reply if this resolves your question ***