Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
Originally Published: 2007-12-27
Article Number
Applies To
Apache Tomcat 5.5.x
Issue
Cause
use.container.credentials=true
Resolution
If setting use.container.credentials to false does not eliminate the null logins, add automaticTestTable="rkmtesttable" to both connection pools specified in kms.xml.
Notes
Related Articles
When terminating a user, the associated GoogleApps account is not disabled in RSA Identity Governance & Lifecycle 19Number of Views Access User Access Review not showing indirect entitlements associated with a role for RSA Identity Governance & Lifecycle… 95Number of Views RSA Identity Governance and Lifecycle user account table control type in the request form does not list all accounts when … 31Number of Views RSA Identity Governance & Lifecycle fails to start with "Connection is not associated with a managed connection" message 91Number of Views RSA Identity Governance and Lifecycle NullPointerException when rules associated with Attribute Synchronization run 161Number of Views
Trending Articles
Troubleshooting RSA SecurID Access Identity Router to RSA Authentication Manager test connection failures RSA SecurID Software Token 5.0.2 Downloads for Microsoft Windows RSA Authentication Manager 8.9 Release Notes (January 2026) Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory RSA Authentication Manager 8.8 Setup and Configuration Guide
Don't see what you're looking for?