Before you set up the Mideye endpoint: decisions and checks

This page is for the administrator who prepares a first installation. When you finish it, you know which backend you use and you have everything the later steps need, so none of them stops halfway.

Before you begin

• A Windows computer for testing: Windows 11 or Windows Server 2019, 2022 or 2025 (x64). A virtual machine is fine. See Requirements.
• Local administrator rights, and no older Mideye Credential Provider installed.
• The installer, mideye-credential-provider-<version>-x64.msi, from the download portal.
• A second administrator session you can keep open until you have tested.
• A test user with a mobile phone number or a token.

Steps

1. Choose the backend. It decides where users, phones and tokens live. Mideye Cloud needs a client ID and client secret from portal.prod.mideye.com. Mideye Server needs a Mideye Server 6.6.6 with an Authentication API endpoint and its API token. Compare them in Choose your backend.
2. Choose how the computer is managed. Standalone: you configure the computer in Mideye Configuration. Fleet: a policy from Mideye Fleet. You can start standalone and join Fleet later.
3. Check the network. The computer must reach the backend over HTTPS before anyone is signed in. See Requirements.
4. Choose the break-glass account and who keeps the break-glass code. It is your way back in, and protection cannot be turned on without it. See Break-glass.

Verify

You can name the backend, standalone or Fleet, the break-glass account, and who keeps the break-glass code. The test computer reaches the backend URL over HTTPS.

Troubleshooting

• The installer refuses when an older Mideye Credential Provider is installed. Uninstall it first.
• A computer that cannot reach the backend cannot sign anyone in once protection is on. Check firewalls and proxies now, see Requirements.

Next: Install.