Invalid username/password : Intermittent error

Shekhar Sharma

We are facing invalid username/ password api error intermittently. It is causing issue with corresponding api interfaces. Need help if we can troubleshoot the issue somehow.

2020-09-26 12:21:31,8530 TRACE [10] BasicServiceContext(): fServer = localhost, fServerPort = 2099, fServerEncoding = UTF8

2020-09-26 12:21:31,8530 TRACE [10] Service()

2020-09-26 12:21:31,8530 TRACE [10]   IServiceContext = BasicServiceContext[fServer=localhost,fServerPort=2099,fServerEncoding=UTF8]

2020-09-26 12:21:31,8530 TRACE [10]   IRequestContext = BasicRequestContext[fClientIPAddress=10.201.191.10,fServiceToken=,]

2020-09-26 12:21:31,8530 TRACE [10] begin: Authentication.AuthenticateUser(BL_TIBCO,<password>)

2020-09-26 12:21:31,8842 TRACE [10] ThrowLivelinkException( -2147482645,Invalid username/password specified.,,,urn:Core.service.livelink.opentext.com)

2020-09-26 12:21:31,8842 WARN [10] Livelink error occurred

2020-09-26 12:21:31,8842 WARN [10]   Status: -2147482645

2020-09-26 12:21:31,8842 WARN [10]   Error Code: Invalid username/password specified.

2020-09-26 12:21:31,8842 WARN [10]   Error Message: Invalid username/password specified.

2020-09-26 12:21:31,8842 WARN [10]   ApiError: 

Appu Nair

Most times it is because the session cookie that you originally got as part of authentication code is being rejected by the livelink server .if you have a server farm comprising of 3 nodes and if one of them gave you the cookie the other two will not like it based on default settings . So what do you do . You can create a sticky connection or relax CS settings but still cookies have expiration like 30 minutes or so . OT addresses this in two ways when you get a soap cookie you know how long it can stay alive so you program with that assumption. Or if you switch to Rest every call in rest gives you a refreshed cookie , but in rest we call them
A header token. If some of these things can be checked that is where I would spend my money . In very old settings the lapi timeout will affect but again tampering all of that is only done at advice of OT because if you allow a socket to stay open indefinitely it will just leak memory and cause DOS kind of attacks possible

Please build your LLserver with same OT home or at least make sure the cookie key encryption is also identical on nodes