Enhanced Security Measures in Place: To ensure a safer experience, we’ve implemented additional, temporary security measures for all users.
02-28-2024 07:17 AM
We're currently trying to implement GlobalProtect and already have some ldap authentication issues with a small test group. We've found out that some special characters (like §) seem to cause issues in passwords. The error is always: Authentication failed: Invalid username or password
The password is not wrong since authentication works on every Windows machine. Is there a list of password requirements for GlobalProtect or anything else we can try to fix this issue?
GlobalProtect version 6.2.2-259 with PanOS 10.2.7-h3.
02-29-2024 12:41 AM
So another thing I've found out: This seems to only affect logins on the Connect Before Logon screen. Standard VPN logins seem to work.
However this doesn't seem to be a general issue on the Windows lockscreen, since Start Before Logon for Cisco Anyconnect works with the same password.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!
