SSO login and local account login fail

Products

• CA Test Data Manager (Data Finder / Grid Tools)

Issue/Introduction

SSO LOGIN button is grey out, login with local accounts also fail.

Log shows:

2026-08-03 00:02:45.942 EDT [WARN ] [https-jsse-nio-8443-exec-187] --- [U:][M:][P:]                      o.h.e.j.s.SqlExceptionHelper:  SQL Error: 18456, SQLState: 08S01
 2026-08-03 00:02:45.942 EDT [ERROR] [https-jsse-nio-8443-exec-187] --- [U:][M:][P:]                      o.h.e.j.s.SqlExceptionHelper:  Kerberos Login failed: Integrated authentication failed. ClientConnectionId:<id 1> due to javax.security.auth.login.LoginException (Receive timed out)
 2026-08-03 00:02:45.942 EDT [ERROR] [https-jsse-nio-8443-exec-187] --- [U:][M:][P:]              c.c.t.c.e.h.GlobalExceptionConvertor:  HTTP Error - SERVICE UNAVAILABLE: Unable to acquire JDBC Connection [Kerberos Login failed: Integrated authentication failed. ClientConnectionId:<id 1> due to javax.security.auth.login.LoginException (Receive timed out)] [n/a]
 2026-08-03 00:05:29.251 EDT [WARN ] [https-jsse-nio-8443-exec-135] --- [U:][M:][P:]                      o.h.e.j.s.SqlExceptionHelper:  SQL Error: 18456, SQLState: 08S01
 2026-08-03 00:05:29.251 EDT [ERROR] [https-jsse-nio-8443-exec-135] --- [U:][M:][P:]                      o.h.e.j.s.SqlExceptionHelper:  Kerberos Login failed: Integrated authentication failed. ClientConnectionId:<id 2> due to javax.security.auth.login.LoginException (Receive timed out)
 2026-08-03 00:05:29.252 EDT [ERROR] [https-jsse-nio-8443-exec-135] --- [U:][M:][P:]      c.c.t.a.s.IDPRelyingPartRegistrationResolver:  Failed to resolve SSO configuration due to 'Unable to acquire JDBC Connection [Kerberos Login failed: Integrated authentication failed. ClientConnectionId:<id 2> due to javax.security.auth.login.LoginException (Receive timed out)] [n/a]'
 java.net.SocketTimeoutException: Receive timed out

Environment

TDM docker portal 5.0.48.0

Cause

For each connection attempt, there was a different ClientConnectionId assigned, which should indicate the tcp connect and preloging to SQL server succeeded.

The SocketTimeoutException for Kerberos should indicate the TDM sent a Kerberos request but no reply arraived within the timeout.

It's likely the environment changed (on KDC side) caused all connections(to GTREP database) in the pool currupted but TDM was not aware of it.

Resolution

Restart TDM fixes the issue. (That forces TDM to re-establish connections)