Native VPN not connecting after integrated with SAML Identify provider.

cancel
Showing results for 
Search instead for 
Did you mean: 

Native VPN not connecting after integrated with SAML Identify provider.

L2 Linker

( 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?

 

2 REPLIES 2

Cyber Elite
Cyber Elite

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? 

L2 Linker

@BPry Yes, Native VPN Client that is in Device

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!