HaroldA.87805 (Customer) asked a question.
Got a weird one in regards to Okta MFA for RDP. I have a handful of users that get "Multi-Factor Authentication Failed" when logging into our Remote Desktop Servers with the Okta Windows Credential provider installed. What is strange is I can log into these same servers with that users account, and I get logged in fine. Up to this point, I could have never imagined that there would be anything client side that can affect whether the user is processed correctly or not by Okta, yet here we are. I have a pending ticket open with Okta about this, but they appear to be as stumped as I am right now. When the users account failed to logon by the widget, I can see in the C:\Program Files\Okta\Okta Windows Credential Provider\Logs\OktaWidget.log, this user is getting the "The remote server returned an error: (401) Unauthorized." Normally in seeing this error, I would check to make sure the user is active in Okta, and is assigned to the Microsoft MFA for RDP application, and they are. And once again, this user can sign on just fine in the same servers on a different workstation, so it can't be a configuration problem in Okta. Has anyone seen anything like this? What things should I be looking for client side that could possibly impact the Okta widget on the remote server working vs not working?
Hi @HaroldA.87805 (Customer),
Thank you for posting on the Okta community page!
Based on the behaviour explained it seems that the issue resides on the user workstation therefore I would suggest to make sure that the user's device is authorised to use RDP.
I would also advise to try and capture a WireShark trace while replicating the behaviour to see if there are any errors reported there that might indicate the root cause of the issue.