Enabling Integrated Windows authentication (IWA) for a site - HxGN SDx - Update 31 - Installation & Upgrade

Installation and Setup for HxGN SDx Application Server

Language
English (United States)
Product
HxGN SDx
Search by Category
Installation & Upgrade
SmartPlant Foundation / SDx Version
10

There are two IIS authentication scenarios for which the software can be configured:

  • Anonymous Authentication - can be used for running all server-side processes, in which case these are the only SDx/IIS users. This is the default configuration.

  • Integrated Windows Authentication - passes client user credentials to the server to be used by IIS to run server-side processes, making all domain users SDx/IIS users.

The Windows Authentication server feature must be installed on the application server in order to enable IWA.

Enabling Integrated Windows Authentication (IWA) as the authentication method for a server site would use domain user accounts to authenticate internal services, such as Business Intelligence reports or other components, such as the License Service.

If you want to use integrated Windows Authentication on a license server, you must set the type of security to use for your license server site. For more information, see Configure integrated Windows Authentication (IWA) for the license server.

Enable Integrated Windows authentication (IWA)

  1. Select a site in the tree view, and click Tools > Enable Integrated Windows Authentication.

  2. Set the application pool identity to a domain user or a local user.

    This user will be added to the SPFUsers group so that it will have permissions to run the SDx Server application pools.

To enable Windows Authentication, your HxGN SDx application pool identity must be set to a domain user or a local user account that is a member of the SPFUsers group on that server.

Disable Integrated Windows authentication (IWA)

  1. Select a site in the tree view, and click Tools > Disable Integrated Windows Authentication.

  2. Select the option required to set the application pool identity:

    • Set the application pool identity back to the default Server Manager user settings.

      For example, when you create a site, Server Manager creates an application pool with a local user as the application pool identify. So, if you name the server SPF2019, by default Server Manager creates an application pool named SPF2019 with a default local user named SPF2019. The default application pool identity in this example is the local user SPF2019.

    • Keep the existing domain user as the application pool identity, but the user must be in the SPFUsers group.

    • Set the application pool identity to the local user you specify.

Manually enable Integrated Windows authentication (IWA)

You need to perform the following actions on your SDx Server virtual directory in IIS:

SHARED Tip The Tools > Enable Integrated Windows Authentication command automates this procedure.

  1. Manually set the application pool identity to a domain user or local user in the SPFUsers group.

  2. Set Anonymous Authentication setting to Enabled (all others disabled).

  3. Set the ServerRequest.asmx setting to IWA Enabled (all others disabled).

  4. Set the Ping.html setting to IWA Enabled (all others disabled).

  5. Set the SPFBaseService.asmx setting to IWA Enabled (all others disabled).

  6. Set the SPFGeneralService.asmx setting to IWA Enabled (all others disabled).

  7. Set the SPFService.asmx setting to IWA Enabled (all others disabled).

  8. Set NTLM as the top provider in Windows Authentication.

    If you are using the Intergraph Authorization Server (which was discontinued as of Update 23), you must also edit the Authentication web.config file and set the EnableCookieAuthentication setting to False. This does not need to be performed if you are using any other authorization server.