Support Article
Unable to access Tenant URL in 8.3
SA-90040
Summary
Post upgrading Pega Platform 7.4 to Pega Platform 8.3, unable to access multiple existing tenants.
Error Messages
Tracer displays: 500 and 403 error
com.pega.pegarules.pub.context.PRSecurityException: Undefined tenant configuration
at com.pega.pegarules.session.internal.engineinterface.service.HttpAPI.validateContextConfig(HttpAPI.java:6902) ~[prprivate-session.jar:?]
at com.pega.pegarules.session.internal.engineinterface.service.HttpAPI.getTenantInfo(HttpAPI.java:6881) ~[prprivate-session.jar:?]
at com.pega.pegarules.session.internal.engineinterface.service.HttpAPI.validateTenant(HttpAPI.java:6849) ~[prprivate-session.jar:?]
at com.pega.pegarules.session.internal.engineinterface.service.HttpAPI.findRequestorInternal(HttpAPI.java:1606) ~[prprivate-session.jar:?]
at com.pega.pegarules.session.internal.engineinterface.service.HttpAPI.findRequestor(HttpAPI.java:1549) ~[prprivate-session.jar:?]
at com.pega.pegarules.session.external.engineinterface.service.EngineAPI.processRequest(EngineAPI.java:354) ~[prenginext.jar:?]
at com.pega.pegarules.session.internal.engineinterface.service.HttpAPI.invoke(HttpAPI.java:916) ~[prprivate-session.jar:?]
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._invokeEngine_privact(EngineImpl.java:331) ~[prprivate-session.jar:?]
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.invokeEngine(EngineImpl.java:274) ~[prprivate-session.jar:?]
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.invokeEngine(EngineImpl.java:251) ~[prprivate-session.jar:?]
at com.pega.pegarules.priv.context.JNDIEnvironment.invokeEngineInner(JNDIEnvironment.java:275) ~[prpublic.jar:?]
at com.pega.pegarules.priv.context.JNDIEnvironment.invokeEngine(JNDIEnvironment.java:220) ~[prpublic.jar:?]
at com.pega.pegarules.web.impl.WebStandardImpl.makeEtierRequest(WebStandardImpl.java:743) ~[prwebj2ee.jar:?]
Steps to Reproduce
- Open a new browser.
- Launch the New Tenant URL.
Root Cause
A backwards compatibility defect in Pegasystems’ code or rules.
In the earlier versions of the Pega application, there was an issue related to the padding character used in encoding. This was resolved in the earlier version by manually editing the generated URL hash. However, this made the existing URLs from the prior versions, invalid.
Resolution
This featuer is implemented in Pega Platform 8.3.1.
Published November 19, 2019 - Updated December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.