Windows Server RDP double lgoin
I have RSA SecureID Authentication Agent installed on Windows Server 2016. It is asking for the windows credentials to start the RDP session, then prompting for the RSA pin, and then prompting again for the Windows credentials.
I see older KB articles about this being an issue that can not be resolved. Is that still the case, or is there some work around that I have not found yet?
To be honest that makes it a deal breaker for us if it has not been resolved. So, hoping someone has some good news.
- Auth Agent
- Authentication Agent
- Community Thread
- Forum Thread
- RSA SecurID
- RSA SecurID Access
We got rid of the 1st windows credential prompt by adding "allow delegating of default credentials" on the domain workstations that need to connect via RDP to this Server.
(doesn't help for non-domain joined machines but I thought I'd mention it)
I also have another issue where during the 2nd prompt for windows credentials (after successfully authenticating the RSA passcode) that is on several occasions the windows password isn't accepted and when I try the logon again a bit later it does work.
Initially I thought I was mistyping my password (but other test users were reporting this as well...) still haven't figured out what causes that.
and in the windows eventlog I clearly see it is registered as bad password attempt.
Failure Reason: Unknown user name or bad password.
Sub Status: 0xC000006A
This pretty much makes this solution unreliable/useless for us.
related products used.
RSA auth agent for windows 7.3.3
RSA auth manager 8.1 sp5
actually on my 2nd issue, the valid Windows password not being accepted, it seems that this is a bug on how that input field is being parsed.
for example just adding a Pound Sign "£" in or at the end of my test password .. breaks the login attempt in the 2nd windows password prompt. (Would be great if someone from RSA would confirm this .. is a known issue or not)