Although IWA SSO may work if you choose not to configure your browser, Okta recommends that you review the relevant information for your browser type and then configure your browser.
IWA is enabled automatically in Safari on OS/X. Make sure that the OS/X host is a Windows domain member. For how to add your Macintosh OS/X host to a Windows domain, see the article OS X Mountain Lion: Join your Mac to a network account server.
The following configuration permits Firefox to properly pass the Kerberos ticket with IWA, but Firefox still warns the user about the transition from an HTTPS page to an HTTP page. To resolve this issue, deploy IWA in HTTPS mode.
- In the Firefox address bar, enter about:config
Note: Firefox3.x and later displays a warning message requesting that you proceed with caution.
- After the configuration page loads, enter the following in the Search field:
- In this field list the host name of the IWA server(s), separating multiple values with a comma ',' if two or more IWA instances are deployed.
Note: The order does not matter if you enter more than one host name.
We recommend that you enter the fully qualified domain name (FQDN) of your IWA host servers. If you do not, you will also need to toggle the following values to TRUE:
- Right click the Value column for each of the above and toggle the value to True.
- Click OK.
IWA capability is enabled automatically in Chrome on OS/X, and just like on Windows, the capability is governed by a allowlist. If a site asks your browser to provide the Kerberos ticket, the browser only provides the ticket if the site is on the allowlist.
- Launch the Terminal application.
- Create a Kerberos ticket for the account:
. . . replacing email@example.com with your actual username and domain. Enter your password when prompted.
- Configure the Chrome allowlist:
$ defaults write com.google.Chrome AuthServerWhitelist "*.example.com"
$ defaults write com.google.Chrome AuthNegotiateDelegateWhitelist "*.example.com"
. . . replacing example.com with your actual domain.