Mutual Authentication Troubleshooting Tips

  • LAN traces:

    • Check the SSL handshake and look at trusted root list that was returned.

    • The client certificate issuer must be in the identity provider certificate store and be applied to all the devices in a cluster.

    • Ensure that the user exists and meets the authentication criteria. As the user store administrator, you can search for a subject name (or certificate mapping attributes defined) to locate a matching user.

  • Enable the Show Certificate Errors option on the Attributes page for the X.509 authentication class. (Click Identity Servers > Servers > Edit > Local > Classes > [x.509] > Properties.) Enabling this option provides detailed error messages on the login browser, rather than generic messages.

  • Ensure that the certificate subject name matches the user you log in with, if you are chaining methods.

  • Use NTRadPing to test installations.

  • Verify that the correct UDP port 1812 is specified.

  • Verify that the RADIUS server can accept requests from Identity Server. This might require the NAS-IP-Address attribute along with credentials.

  • Verify that the user exists in the user store if multiple methods are added to a contract.

  • Verify that user authentication works independent of Access Manager.

  • Verify that the NMAS server is local and no tree walks are occurring across the directory.

  • Ensure that the NMAS_LOGIN_SEQUENCE property is defined correctly.