ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
LDAP User Authentication User Validates and then Asks about Unique User
Article ID: 143835
Updated On:
Products
CA Test Data Manager (Data Finder / Grid Tools)
Issue/Introduction
Does this mean error mean CA TDM is finding the user 2x in LDAP tree?
at java.lang.Thread.run(Thread.java:748)
2019-10-21 13:21:57.028 UTC [INFO ] [https-jsse-nio-8443-exec-16] --- [U:angamv9][M:GET][P:/api/ca/v1/tdod/visualTestFlows] c.c.t.t.s.TDoDServiceAuthClient: Valid SessionId: 1603769739
2019-10-21 13:27:41.466 UTC [INFO ] [https-jsse-nio-8443-exec-15] --- [U:][M:][P:] c.c.t.s.s.SecurityUserService: User 'marcy5' is dn 'CN=Marcy\, AliBaba,OU=Users,OU=CDP,DC=TDDDD,DC=com'
2019-10-21 13:27:41.829 UTC [ERROR] [https-jsse-nio-8443-exec-15] --- [U:][M:][P:] c.c.t.a.c.AuthController: User authentication is successful, but rejected due to the following reason
com.ca.tdm.common.exception.AuthenticationException: User DN for user [marcy5] has changed to [CN=Marcy\, AliBaba,OU=Users,OU=CDP,DC=TDDDD,DC=com] - please check for unique users.
at com.ca.tdm.security.service.SecurityUserService.updateAuthorityNameAndDN(SecurityUserService.java:395)
2019-10-21 13:21:57.028 UTC [INFO ] [https-jsse-nio-8443-exec-16] --- [U:angamv9][M:GET][P:/api/ca/v1/tdod/visualTestFlows] c.c.t.t.s.TDoDServiceAuthClient: Valid SessionId: 1603769739
2019-10-21 13:27:41.466 UTC [INFO ] [https-jsse-nio-8443-exec-15] --- [U:][M:][P:] c.c.t.s.s.SecurityUserService: User 'marcy5' is dn 'CN=Marcy\, AliBaba,OU=Users,OU=CDP,DC=TDDDD,DC=com'
2019-10-21 13:27:41.829 UTC [ERROR] [https-jsse-nio-8443-exec-15] --- [U:][M:][P:] c.c.t.a.c.AuthController: User authentication is successful, but rejected due to the following reason
com.ca.tdm.common.exception.AuthenticationException: User DN for user [marcy5] has changed to [CN=Marcy\, AliBaba,OU=Users,OU=CDP,DC=TDDDD,DC=com] - please check for unique users.
at com.ca.tdm.security.service.SecurityUserService.updateAuthorityNameAndDN(SecurityUserService.java:395)
Cause
The LDAP USER DN was changed on LDAP, but never updated in the TDM Repository.
Environment
Release : 4.7.113
Component : CA Test Data Manager - TDM Web Portal
Resolution
Changed the USER_DN column in TDM Repository manually to reflect the correct USER DN that was in LDAP and it fixed the problem.
Additional Information
We have a patch for this if not wanting to update manually. Open a new support can and refer to Defect DE445710
Feedback
Yes
No
Powered by
