Post-installation Verification

After installing the agent, complete these steps to confirm the Credential Provider is active and authentication is working before rolling out to users.

---

Step 1 - Verify the Agent Appears on the Login Screen

1. Restart the workstation if you have not already done so. The Credential Provider needs a restart for install completion
2. On the Windows login screen, confirm the 1Kosmos tile is visible in Sign-In options.
3. The tile displays the 1Kosmos logo. If you have configured a custom logo via the ProviderIcon registry key, your organisation's logo will appear instead.

If the 1Kosmos tile is not visible after restart:

• Confirm the installation completed without errors. Check logs at C:\Program Files\1Kosmos\1KosmosCredentialProvider\Logs.
• Confirm tenantUrl and communityName are correctly configured in the Windows Registry (MSI) or REGCONFIG.ini (EXE)
• Confirm all runtime dependencies are installed
• See Troubleshooting for further guidance

---

Step 2 - Verify Connectivity to the 1Kosmos Platform

Before testing authentication, confirm the workstation can reach the 1Kosmos platform.

1. Open a browser on the workstation and navigate to your tenant URL (e.g., https://acme.1kosmos.net).
2. Confirm the page loads without certificate errors or timeouts.
3. If the page does not load, review your Network & Connectivity Requirements and proxy configuration, see Troubleshooting & Support.

---

Step 3 - Test Login with MFA

Perform a test login using a user account that has an Adaptive Auth Journey configured in AdminX.

1. On the Windows login screen, click the 1Kosmos tile.
2. If prompted, enter the username.
3. Complete the configured authentication method (e.g., enter password then approve push notification).
4. Confirm the user is successfully logged into Windows.

If the test fails, check the following:

• The user exists in the connected Active Directory or LDAP directory.
• An Adaptive Auth Journey is configured for the user or their AD group under Applications > Windows MFA in AdminX.
• The user has the required authentication method enrolled (e.g., 1Kosmos mobile app linked for Push / TOTP; 1Key enrolled for FIDO).
• Check log files at C:\Program Files\1Kosmos\BlockIDCredentialProvider\Logs for error details.
• See Troubleshooting for common failure scenarios.

Always test with a non-administrator account first. Local administrator accounts bypass 1Kosmos MFA by design — a successful local admin login does not confirm the agent is working correctly.