If users are having trouble authenticating with Mi-Token, here are some things to check:
- Check the Windows Event logs, especially the Mi-Token (Authentication) and System logs for any errors related to the authentication process.
- Review the Mi-Token Reporting console to see if there are any authentication errors or failures logged there.
- Ensure that PAP (Password Authentication Protocol) is enabled in the relevant NPS policy. Mi-Token requires PAP to be enabled.
- Double-check that the RADIUS shared secret configured in NPS matches the shared secret configured on the authenticating device (e.g. VPN appliance).
- Verify the user has been granted remote access permission in their AD user account properties.
- If authentication succeeds with the Mi-Token RADIUS testing tool but fails with the actual device, check if the device has any password length limitations. Some devices truncate longer passwords/secrets which can cause Mi-Token authentication to fail.
If you've checked all these items and authentication is still failing, contact Mi-Token support for further assistance, providing relevant logs and configuration details.