For details on cookie usage on our site, read our Privacy Policy
Native VPN not connecting after integrated with SAML Identify provider.
- LIVEcommunity
- Discussions
- General Topics
- Native VPN not connecting after integrated with SAML Identify provider.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Printer Friendly Page
Native VPN not connecting after integrated with SAML Identify provider.
- Mark as New
- Subscribe to RSS Feed
- Permalink
09-23-2021 12:46 AM
( description contains 'failed authentication for user \'xxxxxxx\'. Reason: Internal error, e.g. network connection, DNS failure or remote server down. auth profile \'AZURE-MFA\', vsys \'vsys1\', From: xxxxx.' )
The above error is getting after introducing the SAML in mobile same we tested from the Laptop and it working without any issues.
For testing, I reverted the authentication to LDAP and it started working.DId anyone have the clue about this issue?
- Mark as New
- Subscribe to RSS Feed
- Permalink
09-23-2021 06:48 PM
When you say Native VPN do you mean like the native VPN client built into the device @CyberEye? I'm assuming that by native VPN you aren't talking about the GlobalProtect VPN client?
Show your appreciation!
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!
