topic Changing the GlobalProtect Portal & Gateway ports in General Topics

Changing the GlobalProtect Portal & Gateway ports

jwolach — Wed, 29 Aug 2012 03:09:42 GMT

Can the GlobalProtect Portal & Gateway ports (443) be changed from 443 to a user defined port number?

Thx

Re: Changing the GlobalProtect Portal & Gateway ports

UhMayYeah — Wed, 29 Aug 2012 04:13:02 GMT

No,this setting is non-configurable .

-Ameya

Re: Changing the GlobalProtect Portal & Gateway ports

rvanderveken — Fri, 25 Jan 2013 08:52:11 GMT

Hi,

There is a workaround that you can use to access the portal on a non-standard port:

Can GlobalProtect Portal Page be Configured to be Accessed on any Port?

Rgds

Raf

Re: Changing the GlobalProtect Portal & Gateway ports

fatboy1607 — Thu, 07 May 2020 12:40:29 GMT

still no solountion to this issue ?

Re: Changing the GlobalProtect Portal & Gateway ports

rkramer — Wed, 23 Sep 2020 15:14:26 GMT

Create your GP portal on a loopback IP, and then use NAT and security rules to drive traffic to that from whatever port you want. I'm using 44443 now as a test and it works perfectly.

Re: Changing the GlobalProtect Portal & Gateway ports

BenSalmonAUS — Mon, 11 Jul 2022 04:57:03 GMT

What if you're trying to use SAML Authentication? The Assertion URL contains :443 and when you are logged in you're redirected back to the wrong port.

Re: Changing the GlobalProtect Portal & Gateway ports

Gustavo_Aristi — Tue, 09 Aug 2022 17:25:42 GMT

Like some have already mentioned, this is indeed possible through a loopback interface.

Here's a working link to this KB:

https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClGKCA0

If GlobalProtect is in Azure (SAML), make sure to change the port here to your desired one:

Re: Changing the GlobalProtect Portal & Gateway ports

BenSalmonAUS — Thu, 11 Aug 2022 01:49:15 GMT

Hi Gustavo,

Thank you for the reply but unfortunately I'm using Duo and not Azure as my SAML IdP and the workaround described in the KB doesn't work. Setting the Login URL seems to do nothing and setting the ACS/Reply URL creates an error saying that the ACS URL doesn't match the URL in the Assertion. Even creating multiple ACS entries doesn't help, it just sends you back to the URL in the Assertion generated by the Palo.

I tried to find out from Duo if the workaround described in the KB is non-compliant SAML that just happens to work or if the functionality of the Duo system was incomplete but I couldn't get a clear answer.

Fortunately I was able to get this working as the customer could request an additional public IP address from their ISP and we were able to put GlobalProtect on 443 on the new IP address.

Re: Changing the GlobalProtect Portal & Gateway ports

NachoR — Mon, 17 Oct 2022 17:25:59 GMT

I try this solution, and doesn´t work. My port is a 7000, when i try a redirect port in azure, the port is always the same 443 not 7000, only with saml