Native VPN not connecting after integrated with SAML Identify provider.

[CyberEye]

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

[BPry]

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? 

[CyberEye]

@BPry Yes, Native VPN Client that is in Device

[SaurabhB]

am also facing the same issue after configuring SAML auth profile for Global Protect. Anybody has any clue, what is wrong ?

[rpogosov]

Is it intermittent or always not working? SAML servers might be failing to respond intermittently: "network connection, DNS failure or remote server down"

[EduRamirez]

The same issue after upgrading to the 10.2.7-h3 version. 

[msnyderman]

What did you have to do to resolve the issue on 10.2.7-h3?

[CyberEye]

@BPry  native means vpn which comes with device not GP

[EduRamirez]

This was solved by doing a commit force after upgrading to 10.2.9-h1.

[EdmarFrancis]

Hi @CyberEye @SaurabhB , hope you are doing well. Any chance you figured out this issue?