To update the FME Server configuration to enable Integrated Windows Authentication (IWA, or "single sign-on") involves the following steps:
Update the user role permissions.
Updating User Role Permissions
Single sign-on users require access to the Token Service to generate security tokens.
Note: You must add your domain's Active Directory security groups as roles before updating permissions. For more information, see "Identify Security Groups" in Connecting to Active Directory.
Updating fmeServerConfig.txt
This configuration file is located at <FMEServerDir>/Server/fmeServerConfig.txt
SECURITY_DEBUG=true
#SECURITY_LOGIN_TYPE=database
SECURITY_LOGIN_TYPE=activedirectory
SECURITY_AD_USE_SASL_AUTHENTICATION=true
SECURITY_AD_SASL_OPTION_MECHANISM=GSSAPI
SECURITY_AD_PREAUTH_USERNAME=<service account name>
SECURITY_AD_PREAUTH_PASSWORD=<service account password>
SECURITY_AD_USE_SINGLE_SIGN_ON=true
Note: SASL authentication must be enabled and Kerberos V5 must be used as the authentication mechanism. Therefore, depending on your Windows domain configuration, SECURITY_AD_SASL_OPTION_KDC_ADDRESS and SECURITY_AD_SASL_OPTION_REALM may be required. For more information, see SECURITY_AD_SASL_OPTION_MECHANISM.
Updating propertiesFile.properties
When FME Server is installed using express installation, this configuration file is located at <FMEServerDir>/Utilities/tomcat/webapps/fmeserver/WEB-INF/conf/propertiesFile.properties.
Verify that the parameter SINGLE_SIGN_ON_AUTH_URL is set to the correct protocol. By default, http is used as the protocol. If SSL is enabled for the web application server, then update the protocol to https.