<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D54z000075XPSyCAOOkta Classic EngineAuthenticationAnswered2024-04-16T11:53:41.000Z2021-08-05T14:26:11.000Z2021-08-08T15:31:43.000Z

5za19 (5za19) asked a question.

Ports for Okta MFA agent on windows

What urls/ips and ports do I need to open in order to set up the okta mfa agent on a windows server? The official documentation just says 443 outbound, but I need more specificity than that.


  • Hello Matthew,

    Thank you for posting!

    The following requirements before installing the Okta Credential Provider for Windows:

    • Proxy Configuration: The Okta Credential Provider for Windows does not support a discrete proxy configuration but will obey system level proxy configurations. To understand management of proxies on Windows machines, refer to www.technet.com.
    • Remote Desktop feature on your computer "hears" the connection request through a defined listening port (3389 by default), refer to https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/clients/change-listening-port
    • The Windows machine used for installation must have an active internet connection with port 443 open.
    • The installing account must have administrative rights to install the Okta Windows Credential Provider Agent, Visual C++ Redistributable and .NET 4.0+.
    • Inline enrollment is not supported.
    • End users must have enrolled their MFA tokens previously, by choosing an MFA option for their account when signing in to Okta the first time or after a reset. End users cannot enroll a token during an RDP sign in. End users with unenrolled tokens receive an authentication failed response from Okta when attempting to sign into an RDP server.

     

    Expand Post
This question is closed.
Loading
Ports for Okta MFA agent on windows