Okta Credential Provider for Windows


The Okta Credential Provider for Windows prompts users for MFA when signing in to supported Windows servers and workstations with an RDP clientEssentially, a client is anything that talks to the Okta service. Within the traditional client-server model, Okta is the server. The client might be an agent, an Okta mobile app, or a browser plugin. . It supports all Okta-supported MFA factors except Windows Hello and U2F tokens.

Additionally, as a Beta feature, end usersIn Okta literature, we generally refer to "end users" as the people who have their own Okta home page (My Applications), using chiclets to authenticate into all of their apps. End users do not have any administrative control. When we refer to "users" we are generally referring to the individual(s) who have administrative control. can reset their Active Directory passwords without contacting their administrators. This is done with the Reset Okta Password link on the sign-on screen. If you are using this Beta version, be sure to set the property to enable this feature, as shown in modify additional properties, below. To see about participating in this Beta program, please refer to the Beta Programs page. The current Beta version is 1.2.1.



Sign in to Okta and verify or set up policies. Install the agent on the Windows server and return to Okta to create an appAn abbreviation of application. Essentially, it is a web-based site used to perform any number of specific tasks, and requires authentication from end users by signing in. and assign users. Test the setup once the installation has been successful. The installation contains three major installation steps and one testing step. Be sure to complete the testing after the installation.