Here's something you can try.
In the Site Admin module, change the value of the Domain Authentication field for that user to match the Domain Authentication value for your own user. Then you log in to ALM using that user's login name but your own AD password.
The way LDAP authentication works for ALM is like this.
1. User enters their login name and password into the ALM login screen.
2. ALM takes just the user login name, and looks for a match in the Site Admin User table.
3. If a match is found, ALM takes the Domain Authentication information, and the password entered, and tries to validate the user via LDAP.
ALM doesn't actually use the user's login name during the LDAP authentication process. So, it doesn't really matter what the login name is. It only matters that is is mapped, in Site Admin, to a Domain Authentication value that is valid, and that the password entered is a match for the user specified in the Domain Authentication value.
In the Site Admin module, change the value of the Domain Authentication field for that user to match the Domain Authentication value for your own user. Then you log in to ALM using that user's login name but your own AD password.
The way LDAP authentication works for ALM is like this.
1. User enters their login name and password into the ALM login screen.
2. ALM takes just the user login name, and looks for a match in the Site Admin User table.
3. If a match is found, ALM takes the Domain Authentication information, and the password entered, and tries to validate the user via LDAP.
ALM doesn't actually use the user's login name during the LDAP authentication process. So, it doesn't really matter what the login name is. It only matters that is is mapped, in Site Admin, to a Domain Authentication value that is valid, and that the password entered is a match for the user specified in the Domain Authentication value.