Creating an Authenticated Tunnel from One Internal Zone to Another Internal Zone

[RSteffens]

I would like to create a secure internal tunnel such that a user requires authentication (ideally MFA, or a cert, or at least a PW, etc)  to get from one internal zone to another internal zone (ie user zone to the management zone).  What are my options?

Is anyone doing this sort of thing with Okta?  Is there a certificate based way to do this?  Other ideas?

If anyone can point me to some materials, or just help me know better what to search for or what the solution is called, I'd be delighted. 

Thanks!

[RSteffens]

So I just found this knowledge base article that sounds like what I want to do. 

https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA14u000000HCEzCAO&lang=en_US%E2%80%A...

Has anyone ever gotten this sort of thing working?  I currently use the Okta Captive Portal for User ID, but again I can only get it working when http/https traffic triggers the captive portal.  This would offer a great way to authenticate traffic between sensitive zones, if I can get it to work. 

[BPry]

Captive Portal will only trigger for users who aren't already authenticated and mapped to the IP via user-id. If you already have a user mapped to the IP it won't trigger anyways, regardless of it not being web traffic. 

[RSteffens]

 So far, that doesn't seem to have caused unwanted behavior for us with the existing Okta captive portal setup.  On zones that use it, it authenticates reliably every time users attempt to access the web zone, repeatedly.  I have not encountered a situation where it fails to authenticate anyone.  It's fantastic because it's both multi factor, and auths against existing database of users in the Okta cloud LDAP.   

If I could just take the exact way its currently working, and prompt for authenticating using captive portal the same way when accessing the management zone, as it does with the web zone. 

[TomYoung · Accepted solution]

Hi @RSteffens ,

Great document find!  Why don't you add the management zone to your authentication policy?  Am I missing something?

Hi @BPry and @OtakarKlier ,

In the newer PAN-OS, the Captive Portal Settings tab under Device > User identification has been renamed Authentication Portal Settings.  When I edit the setting and click on help, I see this message.

So, I don't think it is only for User/IP mapping or only triggers on unknown users in the newer PAN-OS.  Also, in the Authentication Policy, you have a drop down for source users that can specify any, unknown, etc.

I have tested this with GlobalProtect, and I am required to authenticate on the web redirect page.  My User-ID vpn-client data source existed before the captive-portal data source was generated.

I hope this helps,

Tom

[RSteffens · Accepted solution]

Hi! 

This is a bit late, but just wanted to let everyone know that I did indeed get this working using the guides here:

https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA14u000000HCEzCAO&lang=en_US%E2%80%A...

And here:

https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA14u0000001VgsCAE&lang=en_US%E2%80%A...

(although I wasn't integrating Prisma, the basic technique is the same)

This series is also very helpful:

https://live.paloaltonetworks.com/t5/blogs/globalprotect-overview/ba-p/322170 especially part IV

The final result is spectacular and wonderful.  Thanks for all your helpful ideas!