multiOTPCredentialProvider
multiOTPCredentialProvider copied to clipboard
multiOTP
RDP and wrong password
When I try to connect via RDP and enter the wrong user password, the authorization window starts sending a blank password repeatedly until the user is locked out. It's happend when user without 2fa. If user with 2fa, after wrong pass it's send blank pass and open one-time pass
Hello, thanks for your feedback. Can you please send us a video ? And tell us what version of credential provider you are using and which version of Windows you are remotely connecting to ? Best regards
without 2fa https://github.com/user-attachments/assets/d1052528-ee9c-4e09-9600-bb79dd9eb2ea
with 2fa https://github.com/user-attachments/assets/096fa8c0-ce6d-4f89-802e-91cfcceea0ab
CP version 5.9.8.0, Windows Server 2016 and WIndows 10
Hello, I'm not able to reproduce the error. Can you please give us the content of the registry (without the shared secret) where multiOTP credential provider is installed : HKEY_CLASSES_ROOT\CLSID{FCEFDFAB-B0A1-4C4D-8B2B-4FF4E0A3D978}
Best regards
It's happened when CP installed on PC which form I trying to connect to RDP. Even if on remote PC CP is not installed.
CP version 5.9.9.2 same problem
Maybe it's possible to turn of CP for RDP credential form and leave CP for credential form when not privileged user start runing programs as admin or other user?
Are you running RDP client as administrator ? You registry key cpus_credui is set to 0e it means that OTP is asked when you run something that needs elevated rights. Try to set this registry key cpus_credui to the value 3d is it still asking you for OTP ?
Best regards
No, RDP client runs as a normal user. If I set cpus_credui = 3d, OTP is not requested. But I would like to set it to 0e. So that unprivileged users cannot run anything as admin without asking for admin's 2fa. And here we come to the problem with users without 2fa who enter the wrong password in the RDP credentials form
Thanks for the info. We were able to reproduce the bug. We are looking for a solution. We will keep you posted.
Regards
Hello, we found a solution. We plan to release it in the middle of May.
Are you interessted in testing the new dll before release ? If so please send us an email to : [email protected]
Best regards