I know this is an old post. I spent lot of time searching the root cause of this login issue. So I would like to add my comment for those who investigate this issue in future.
If the password has '@' , the LDAP treats it differently and causes the login issue. It can happen with JDBC, CLI, ODBC and .Net. Please refer Teradata Knowledge Article KAP1B0756.
The following the article from Teradata support for KAP1B0756
Teradata Knowledge Base Solution ID: KAP1B0756
Special character in password such as @ prevents LDAP login
LDAP logins fail if the password includes a special character such as an at @ sign. The error indicates "User ID, Password or Account is invalid."
The characters @, / and \ have special meanings in a UPN. If they are encountered in a password, they must be escaped as follows: \@, \/ (backslash followed immediately by forward slash, not capital V)and \.
The problem is documented in DR 119905 for CLIv2 and DR 132857 for ODBC, and is fixed in the following product versions:
CLIv2 126.96.36.199, 188.8.131.52, 184.108.40.206
ODBC 220.127.116.11, 18.104.22.168, 22.214.171.124
Prior to using a fixed version, the workaround is to use the escape character \ prior to the character.
References to Procedures:
There are no attachments on this document.