However, if you sign in to Access Server with "Gary", and the LDAP server returns "gary" as the match, Access Server looks up user-specific properties for "gary". Some LDAP servers may not be case sensitive for usernames, such as Active Directory. Authentication fails if you enter "Gary" to sign in but the actual username is "gary". After a successful match, Access Server can apply user-specific properties-auto-login privileges, static IP address, and so on.įor PAM authentication, the username is case-sensitive. Ensure the username case matches between Access Server and the external authentication system. Most authentication systems are case-sensitive. authcli -user -pass -sr= Case-sensitive matters for usernames Verify authentication for a user with multi-factor authentication (MFA) enabled. Sample output of a successful local authentication attempt: API METHOD: authenticate Note: Mismatched usernames are one of the most common problems with authentication, where the username in the User Permissions table for OpenVPN Access Server doesn’t precisely match the username in the external authentication system.Ĭhoose from the below commands for debugging or testing with authcli. To run authcli, ensure you are in the /usr/local/openvpn_as/scripts/ directory and run the commands as a root user. You can print authentication results to your screen, see user-specific properties applied when authentication succeeds, and verify if expected properties get picked up. The authcli tool runs tests and provides useful debugging information in the process. To validate your authentication configuration for OpenVPN Access Server, we recommend using the authcli command-line utility. Debugging / troubleshooting authentication problems Use the authcli tool
0 kommentar(er)
