"Internal Server Error" is displayed in the browser when logging into the portal.
"Internal Server Error" is a non-specific message that indicates a technical problem occurred that prevented RSA SecurID Access from responding to a request. More information is usually recorded in the RSA SecurID Access system log.
If this error is seen when the user is logging into the Portal, it is likely because of a problem connecting to the LDAP or Active Directory (AD) server being used to authenticate the user. Some common causes for a technical issue preventing authentication with LDAP/AD are:
A network outage or error between the Identity Router (IDR) and the LDAP or AD server.
Misconfigured DNS entry for the LDAP or AD server.
The LDAP or AD server is not configured correctly in the RSA SecurID Access Administration Console.
Invalid credentials (user ID and/or password) configured for LDAP/AD in the RSA SecurID Access Administration Console.
Check the RSA SecurID Access IDR system logs for events at the time of the "Internal Server Error" message, that may indicate the reason for the issue. An example is:
2016-08-12/14:58:51.538/UTC [ajp-apr-8009-exec-9] WARN com.symplified.service.shared.authnengine.AuthenticationEngineImpl -
Error occurred while trying to authenticate against user store <store-name> com.symplified.adapter.api.userstore.ldap.LdapUserStoreException:
Failed to create initial dir context for LDAP connection. LDAP server is '<server-fqdn-or-ip>' principal is '<user id>'.
CAUSE: [LDAP: error code 49 - 80090308: LdapErr: DSID-0C0903C8, comment: AcceptSecurityContext error, data 52e, v2580]
In this case "LDAP: error code 49 - 80090308: LdapErr: DSID-0C0903C8, comment: AcceptSecurityContext error, data 52e, v2580" is a Microsoft Active Directory error message, indicating a likely problem with the AD credentials configured in RSA SecurID Access, possibly a password issue. Contact Microsoft Support if assistance is needed with troubleshooting Active Directory errors.
If logged event messages indicate an LDAP/AD issue, check your LDAP/AD configuration in RSA SecurID Access for errors. See the RSA Via Access Help, sections under Identity Sources, for information about configuring LDAP/AD in RSA SecurID Access.