We are using SAML in Azure for GP external gateway connection.
When connection method is on demand we get mobile push notification and user gets connected to the GP.
Testing with Connection method Pre logon Always on, i am not getting mobile push notification.
Need to confirm is this by design?
or is there any config i can do so that Connection method Pre logon Always on gives me mobile push notification?
Solved! Go to Solution.
Hi @MP18 ,
Not sure if this is by design.
I'd recommend reaching out to TAC and have them confirm with engineering if it's by design or not.
I don't really get it. Why isn't this possible exactly? With SAML you get single sign on, but as you have another loginfactor the push notification should be sent - so why not in your configuration? Don't give up too easily with answers from TAC
If there really isn't a way without a feature request where you have to wait, what about using RADIUS MFA connectior for your always-on clients? Does it maybe work this way with SSO and push notifications?
We have Global protect PRe log on Always on for pilot testing.
We have SAML configured where we get the push notifications on mobile for authentication.
We are using Azure SAML.
When user put the domain password during log on then GP client connects automatically they do not get mobile push notifications.
Opened ticket with TAC almost 2 weeks ago and today he confirmed that this is expected behaviour.
We can not force push mobile notifications while using pre log on always on connection method.
Also as our current setup we only want to use SAML using Azure.
You are using the newest GP version? Or at least something above 5.0.2?
(I am asking as I intended to do a similar setup ... but this now does not sound very good ...)
But the push notification is sent by your SAML IdP or the attached MFA service right? And GP officially supports "Pre-logon followed by SAML". So when viewing from the other side: why is this an issue of GP as the IdP is sending or at least triggering the push notification?
We do not have MFA configured.
As per PA while using Global protect External and using SAML you can not have MFA.
I could not find answer for this checked with PA and also with our SE.
Only option is to use on demand connection method.
As per PA we can submit the feature request to them.
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 Live Community as a whole!
The Live Community thanks you for your participation!