Windows Credential Provider Best Practices

Find out more

• Integrating Evo with Windows desktops

• Evo Secure Login for Windows

Tip(s)

• Configure the authentication mode as both, which will allow users to login as either an end-user or an elevated user.

• To login as an elevated account, the user must be assigned an elevated group assignment, that is associated with an appropriate shared account for the tenant.

Steps to Follow

• Install the Evo Credential Provider
• DO NOT select the feature “Evo Login Provider”
• ensure the Environment URL is prefixed with https://
• ensure an access token is filled if authentication mode is Elevated Only or Both
• the Secret Key can be blank if installing over a previous installation was Elevated Only or Both

• Immediately after installation
• DO NOT logoff — stay logged into the same session
• Start Evo Settings Editor
• Selection Connection Test...
• Verify that the user can successfully connect with a Windows username
• Do not move on until successfully connecting. If you cannot connect, verify that the Environment URL and Evo Directory are correct. You can change the settings in the same Evo Settings Editor

• Lock the current session and then try to unlock using the Evo Security login tile. (Other tiles should be available at this point). Make sure you can unlock.

• If you are convinced all settings are correct. Then in the Evo Settings Editor select the Evo Login Only checkbox and click the Apply button

• If you want to save the settings in a JSON file for another installation, start an elevated PowerShell session and run the command "C:\\Program Files\\EvoSecurity\\EvoSecureLogin\\EvoCredProSettings.ps1" -generate With the command, you can either dump it to the screen or re-direct it to a file.

• You can then use the JSON file to install the CredPro on all computers in the domain using the Evo Installation Script (or using ConnectWise RMM)

Script