This should get you pretty close:
Set up GlobalProtect
Add the new captive portal to the portal agent configuration - Network > GlobalProtect > Portals > GP_Portal > Agent
Alias to point to VLAN 961 Example: server.mfa.company.com 10.10.10.10
Set up Azure
Basic SAML Configuration
Identifier (Entity ID) https://server.mfa.company.com:6082/SAML20/SP
Reply URL (Assertion Consumer Service URL) https://server.mfa.company.com:6082/SAML20/SP/ACS
Federation Metadata XML Download
Set up Palo Alto:
SAML Identity Provider
Device > Server Profiles > SAML Identity Provider > Import
Device > Authentication Profile > Add
Type = SAML
IDP Server Profile = SAML Identity Provider created above
Username Attribute = username
Advanced Tab > Allow List = all
Objects > Authentication > Add
Authentication Method = web-form
Authentication Profile = Authentication Profile created above
Policies > Authentication > Pre Rules > Add
Action Tab > Authentication Enforcement > Authentication Object created above
Let me know if you have any questions.
@MP18 I found that one, but there are parts that don't make sense to me.
"Next lets create an authentication profile that will be used in our captive portal, navigate to Objects > Authentication and press “Add”:"
Set the following values and press ok:
Name: Anything you like!
Authentication Method: Browser-challenge (doesn’t really matter here as the request will be redirected to Azure-AD anyway)
Authentication Profile: The Azure-AD authenticaiton profile we setup in the previous section
Message: Leave default- users will not see this anyway.
But then I don't see how that ties into anything???
@MP18 It also says:
n our case we want to that to a FQDN that users using an internal DNS server will point to an internal interface on the firewall. For example https://internal.azureadmin.co.uk:6082/SAML20/SP which would resolve to an internal interface on the firewall (such as 192.168.100.1). The port number here is the port the Palo Alto hosts its captive portal service when enabled.
Reply URL (Assertion Consumer Service URL):
This is the URL that Azure will send the user back to after the SAML authentication processs completes, in our case we can use the same URL as the Identifier- for example- https://internal.azureadmin.co.uk:6082/SAML20/SP
Use the same reply URL? That doesn't seem right?
One thing to remember with Captive portal is that its used only for matching a user to and IP address for mapping. If a use is already known, the portal will not be presented to the user.
Hope that makes sense.
Here is what I'm hoping will happen. User crosses from zone to another and is presented with the CP. User puts in username and password and then gets a push notification to there phone via Microsoft Authenticator. User clicks "approve" and the CP process completes. All internal.
Currently, I have CP set up so that User crosses from zone to another and is presented with the CP. User puts in username and password and the CP process completes.
Is what I'm hoping for possible? Am I explaining it correctly?
If you have not done any CP config then you can also check with your SE How to do it?
Are you the one who will do configuration in Azure?
Also see this
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!