Support Article

Unable to access login page, authentication errors



Developers are unable to log in or even access the login page. The tomcat server is up but the Pega application returns a internal error related to authentication.

Error Messages

Status fail
Message There has been an issue; please consult your system administrator
Operator ID Unauthenticated or not available
Requestor ID No ID available
Timestamp Mon Aug 29 18:07:03 UTC 2016
Engine Version PegaRULES 7.20 ML0 (coreAssemblyCached_72_868)

Steps to Reproduce

Not applicable

Root Cause

A software use or operation error resulted in this issue.

he browser Requestor Type rule for the system was referencing an access group pointing to an application that was recently deleted.

Developers would have been able to continue working, but once logged out, the issue would start appearing.


To resolve this issue, temporarily added the following entry to prconfig.xml:

    <env name="Identification/SystemName" value="pega" />

If the system name was already 'pega', use 'prpc' instead.

​This will allow developers to log back in and make any necessary changes to the browser Requestor Type (Records Explorer > SysAdmin > Requestor Type) before reverting back to the5 original system name.

Published September 6, 2016 - Updated September 14, 2016

Have a question? Get answers now.

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