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

Cases not getting loaded on Designer Studio

SA-10595

Summary



After login to Pega 7 Developer portal, when user click on cases tab and results are not getting loaded. Text message “loading..” shown on the screen instead of cases.
 

Error Messages



Below error is thrown in Pegarules log file generated at user end:
------------------------------------------------- 
2015-06-01 00:00:03,786 [   WorkManager(2)-42] [          ] [                    ] (  priv.context.JNDIEnvironment) ERROR   - Exception during getEJBInstance "com.pega.pegarules.internal.etier.interfaces.EngineLocalHome"
java.lang.reflect.InvocationTargetException
                at sun.reflect.GeneratedMethodAccessor366.invoke(Unknown Source)
 
Caused by: javax.ejb.AccessLocalException: SecurityException
                at org.jboss.ejb.plugins.LogInterceptor.handleException(LogInterceptor.java:384)
                at org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:136)
 
Caused by: java.lang.SecurityException: Authentication exception, principal=null
                at org.jboss.ejb.plugins.SecurityInterceptor.checkSecurityContext(SecurityInterceptor.java:321)

-----------------------------------------------------

Steps to Reproduce



1. Login to PRPC Developer portal
2. Click on cases tab (exists on left side of portal) to list the casetypes.


Root Cause



The root cause of this issue is a defect in configuration of ‘security-domain’ in jboss.xml. 

Resolution



This issue is resolved by making the following change to the operating environment:

 
Modify jboss.xml from prpc_j2ee14_jbossJBM.ear/prbeans.jar by commenting out

<security-domain>java:/jaas/other</security-domain>

And adding:

                                         
<security-domain></security-domain>

Effectively having this:
<!--<security-domain>java:/jaas/other</security-domain>-->
<security-domain></security-domain>
<unauthenticated-principal>anonymous</unauthenticated-principal>


This way, jboss will use the default 'application-policy' named 'other' by not providing a value for 'security-domain' and there is no security risk associated with it.

 

Published June 12, 2015 - 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