You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 27, 2018. It is now read-only.
When using the credentialprovider on a remote desktop 2016 server using AD credentials we need to enter the username and password inside the mstsc client in order to connect to the session host. Once connected we need to enter the username and password again, this time together with a token.
Is this a misconfiguration on our side? Or is it a limitation of the credentialprovider?
A perfect solution would be if the username and password could be pre-populated from the RDP session or not shown at all. Resulting in a window just asking for the OTP.
Any suggestions?
Kind regards (and thanks for the work on this important project!)
The text was updated successfully, but these errors were encountered:
This is a special behaviour when NLA is enabled. Unfortunately, only the Microsoft Credential Provider can use the credential typed at the begininng.
Please note that we have enhanced this MultiOneTimePassword-CredentialProvider thanks to various contributors, and it's now available in the multiOTP project (https://github.com/multiOTP/multiOTPCredentialProvider). We will do enhancements in this fork.
Regards,
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
When using the credentialprovider on a remote desktop 2016 server using AD credentials we need to enter the username and password inside the mstsc client in order to connect to the session host. Once connected we need to enter the username and password again, this time together with a token.
Is this a misconfiguration on our side? Or is it a limitation of the credentialprovider?
A perfect solution would be if the username and password could be pre-populated from the RDP session or not shown at all. Resulting in a window just asking for the OTP.
Any suggestions?
Kind regards (and thanks for the work on this important project!)
The text was updated successfully, but these errors were encountered: