<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
0D51Y00005wDA7ASAWOkta Classic EngineSingle Sign-OnAnswered2023-07-10T08:55:26.000Z2019-02-04T23:55:27.000Z2019-02-05T05:14:35.000Z
  • GabrielL.85945 (Customer)

    I think this is technically possible, but not really a good idea. I'd highly recommend against this.

     

    When a user logs into a domain-joined PC, they will be authenticated by a DC and then issues a kerberos ticket. If the PC is off-network and a DC is not reachable, then the user will not authenticate against a DC and will instead use a cached password. And since you can't connect to a DC, you won't have the kerberos ticket issued. The kerberos ticket is what's used when authenticating with IWA. So you'll have to solve that problem too, along with plenty of others.

     

    The most common solution is to just use VPN. This way, both the IWA server and DC can be made accessible through the VPN.

     

    Okta's Agentless Desktop SSO, which is available as Early Access (EA), may solve some of the problems. Link to documentation with a nice diagram below:

    help.okta.com/en/prod/Content/Topics/Directory/Configuring_Agentless_SSO.htm

    Expand Post
This question is closed.
Loading
Hosting Okta IWA webapp on public network supported?