<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D54z00007wWP17CAGOkta Identity EngineAccess GatewayAnswered2024-01-31T00:36:22.000Z2022-08-15T20:06:55.000Z2022-09-14T17:30:22.000Z
PaloAlto Global Protect fails authentication when connected on Guest Network

When users are connected via guest network at the office, and they try to connect to Okta via Global Protect VPN, the authentication via IWA fails and the error message "Couldn't reach to "IWA Agent.org"" appears. However, without VPN, they can go through. I have added the Public IPs to the Gateway IP list, but it does not seem to work. I also cannot see any attempted login events in the user logs.


  • PaulS.92454 (Customer)

    Hello @Okta AD Agent 3A.98516 (Customer)​ Thank you for reacting out to our Community!

     

    The culprit for this would be the Network zones, as the IP rages need to be added to the "Trusted Proxy IPs" as well. Once you add them there the authentication should go without a problem.

    As per our doc "Enter the Gateway IP addresses and Proxy IP addresses. Separate IPs and IP ranges with a newline or comma. Single IPs, IP ranges or CIDR notation can be added."

    Please also see our doc for this:

    https://help.okta.com/en-us/Content/Topics/Security/network/define-iwa-network-zone.htm

     

    The Okta Community Catalysts Program is now live. Collect online badges when you participate in the Okta Help Center Questions community. Learn more here.

    Expand Post
    Selected as Best
  • PaulS.92454 (Customer)

    Hello @Okta AD Agent 3A.98516 (Customer)​ Thank you for reacting out to our Community!

     

    The culprit for this would be the Network zones, as the IP rages need to be added to the "Trusted Proxy IPs" as well. Once you add them there the authentication should go without a problem.

    As per our doc "Enter the Gateway IP addresses and Proxy IP addresses. Separate IPs and IP ranges with a newline or comma. Single IPs, IP ranges or CIDR notation can be added."

    Please also see our doc for this:

    https://help.okta.com/en-us/Content/Topics/Security/network/define-iwa-network-zone.htm

     

    The Okta Community Catalysts Program is now live. Collect online badges when you participate in the Okta Help Center Questions community. Learn more here.

    Expand Post
    Selected as Best
  • Thank you @PaulS.92454 (Customer)​,

     

    Indeed Network Zones are the problem. With further testing, I found that our Internal Network and Guest Network uses the same BlueCoat Egress IPs. I have defined these IP ranges in both Gateway and Trusted Proxy, however, it still does not work for users on Guest Network. But If I define these IPs in Trusted Proxy only, Guest Network are able to reach and authenticate via Okta, but creates a problem with Internal users.

     

    Expand Post
This question is closed.
Loading
PaloAlto Global Protect fails authentication when connected on Guest Network