Hi,
Thank you very much for this great software!
I recently deployed multiOTP appliance and CredentialProvider internally and it is working well. However, I just realized when initiating an RDP connection that CredentialProvider prompting for a code to start the connection even though I'm logged in as a without2fa user on a workstation where multiOTPWithout2FA is enabled.


This occurs on a workstation on which multiOTPWithout2FA is enabled, but not on another workstation where it is disabled. Both have multiOTPCredentialProvider installed pointing to the same multiOTP appliance, with the following settings:
multiOTPCacheEnabled : 1
multiOTPServerTimeout : 5
multiOTPTimeout : 60
multiOTPUPNFormat : 1
two_step_hide_otp : 1
two_step_send_password : 0
two_step_send_empty_password : 0
cpus_logon : 0e
cpus_unlock : 0e
cpus_credui : 0e
multiOTPTimeoutUnlock : 60
multiOTPDisplayLastUser : 1
multiOTPWithout2FA : 1
Is this expected behavior, or am I missing something?
I'm not sure if this is an issue, but I don't recall this behavior during my initial testing and deployment. It seems unnecessary, since a client connecting to a computer with CredentialProvider is challenged by CredentialProvider whether or not it is installed on the client.
Thanks again!
Hi,
Thank you very much for this great software!
I recently deployed multiOTP appliance and CredentialProvider internally and it is working well. However, I just realized when initiating an RDP connection that CredentialProvider prompting for a code to start the connection even though I'm logged in as a without2fa user on a workstation where multiOTPWithout2FA is enabled.
This occurs on a workstation on which multiOTPWithout2FA is enabled, but not on another workstation where it is disabled. Both have multiOTPCredentialProvider installed pointing to the same multiOTP appliance, with the following settings:
Is this expected behavior, or am I missing something?
I'm not sure if this is an issue, but I don't recall this behavior during my initial testing and deployment. It seems unnecessary, since a client connecting to a computer with CredentialProvider is challenged by CredentialProvider whether or not it is installed on the client.
Thanks again!