Have you actually validated the authentication profile that you're using by running the test authentication authentication-profile command and verified that this is working properly? You should also verify in the logs the actual failure reason being documented by the firewall.
Hi, thanks for the feedback. I've checked by running the command and there's no problem here.
After doing more research, it appears that the settings on Authentication Profile, Portal and Gateway do not play nice with the 'ou=people,dc=domain,dc=local' as 'source user'. GlobalProtect connection will show 'Authentication Failed' with this setting.
But when i changed this to 'all' or 'any' on Authentication Profile, Portal and Gateway, GlobalProtect connection using the user 'dpot' works without any issue.
Please refer to the following screen shots;
Perhaps you have any idea why?
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!