<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
0D51Y00006SmeS8SAJOkta Classic EngineSingle Sign-OnAnswered2024-04-12T22:05:33.000Z2019-07-22T23:42:23.000Z2019-07-30T22:44:12.000Z

lkphk (lkphk) asked a question.

IWA for Multiple Regions, How would the IWA process work?

Hi all,

I have my AD's and users spread over multiple geographical regions, I have installed a IWA in one region but would like to know if i were to install another IWA agent in another region how the IWA process would then work.

Would there be the chance of users from region A being able call the region B IWA?


  • EricK.22493 (Kohl&amp;#39;s)

    If both regions communicate with Okta from a unique IP/range, then you could configure them each with their own network zone and tag that into the IWA routing rule.

     

    https://help.okta.com/en/prod/Content/Topics/Security/Security_Network.htm#IWA

     

    If both regions backhauled to the internet through the same IP/range, then Im afraid you might be limited to internal network "shenanigans". Some sort of network load balancer could probably steer traffic correctly. Or using the same hostname & SSL cert in both regions you could round robin DNS and hope that shortest path is returned by the DNS server.

     

    Is your goal to prevent cross region or allow it?

    Expand Post
    Selected as Best
  • EricK.22493 (Kohl&amp;#39;s)

    If both regions communicate with Okta from a unique IP/range, then you could configure them each with their own network zone and tag that into the IWA routing rule.

     

    https://help.okta.com/en/prod/Content/Topics/Security/Security_Network.htm#IWA

     

    If both regions backhauled to the internet through the same IP/range, then Im afraid you might be limited to internal network "shenanigans". Some sort of network load balancer could probably steer traffic correctly. Or using the same hostname & SSL cert in both regions you could round robin DNS and hope that shortest path is returned by the DNS server.

     

    Is your goal to prevent cross region or allow it?

    Expand Post
    Selected as Best
  • lkphk (lkphk)

    The goal was to allow it, thank you for your response. I had also raised a ticket and received a reply for Okta help Desk, i will leave it here for future reference.

     

    Ticket Reply

    User will simply access the IWA redirect url and based on the location, forwarding will be done and AD agent will be implied. 

    When dealing with Automatic Failover in an IWA environment, there is a health check in place that regularly checks the availability of the IWA apps to ensure they are still running. The health check is done by the AD agent. There is no specific agent that runs the check as this is a random process. The AD Agent, using the local service account, would try to access the IWA URL for a successful response. If the response is a negative one, it will consider that the web app is offline and report that to your Okta tenant. 

     

    Furthermore, the only information that the Okta Service Account(used for the API Integration) will provide is its state. Furthermore, Okta uses a bearer token for API authentication with a sliding scale expiration. Tokens are valid for 30 days and automatically refresh with each API call. 

     

    Example:

    User A is located in Singapore. DC is located in India as well as the AD agent. User A will simply navigate to the org`s URL and will authenticate based on the AD Agent`s permission from India. 

     

    If you would like to install multiple IWA agents, that should be ok, since there is no proprietary agent that would report back and perform authentication on behalf of the user. The web application will use multiple IWA agents for failover purposes. 

     

    Expand Post
This question is closed.
Loading
IWA for Multiple Regions, How would the IWA process work?