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 RSA Identity Governance & Lifecycle fails to start with "Connection is not associated with a managed connection" message 92Number of Views RSA Identity Governance and Lifecycle user account table control type in the request form does not list all accounts when … 33Number of Views RSA Identity Governance and Lifecycle NullPointerException when rules associated with Attribute Synchronization run 162Number of Views Remove groups from multiple disabled Accounts fails with error: "Expected 1 account associated with the ChangeRequestItem.… 81Number of Views
Trending Articles
RSA Authentication Manager 8.9 Setup and Configuration Guide How to 'Trust' the RSA Authentication Manager Security Console Self-Signed Root CA certificate and prevent Cert warnings. RSA Authentication Manager 8.9 Release Notes (January 2026) Configure RSA Authentication Manager as a Secure Proxy Server for Cloud Access Service RSA Authentication Manager Upgrade Process
Don't see what you're looking for?