Summary
Understand the scenarios where the value of “UserNameCaseSensitive” does or does not affect the case sensitivity of the username.
Details
The scenarios where the username is case-sensitive or case-insensitive are listed below.
- All installations of TMEE are case-insensitive. The value of the “UserNameCaseSensitive” policy has no bearing. This is true whether the installation is done by a Group User, PolicyServer Administrator, or PolicyServer Authenticator.
- The initial authentication on the client device for Group Users is case-insensitive. The value of “UserNameCaseSensitive” has no bearing.
- After the initial Group User authentication on the client device, case sensitivity will follow the “Yes” or “No” value of “UserNameCaseSensitive”.
- When a PolicyServer Administrator or Authenticator is authenticating at the login screen on the client device, the username is case-sensitive, regardless of the “UserNameCaseSensitive” setting.
If the username does not match the case of the username on the Policy Server, the authentication will fail. You will get a message in the Diagnostics Monitor that “UserNameCaseSensitive” is set to “True” regardless of the actual value. - When a PolicyServer Administrator or Authenticator is authenticating on the client into the Recovery Console, the username is case-sensitive, regardless of the “UserNameCaseSensitive” setting.
If the username does not match the case of the username on the Policy Server, the authentication will fail. You will get a message in the Diagnostics Monitor that “UserNameCaseSensitive” is set to “True” regardless of the actual value. - When a PolicyServer Administrator or Authenticator is authenticating into the PolicyServer MMC, the username is case-sensitive, regardless of the “UserNameCaseSensitive” setting.
If the username does not match the case of the username on the Policy Server, the authentication will fail. You will get a message in the Diagnostics Monitor that “UserNameCaseSensitive” is set to “True” regardless of the actual value.
