The Gateway Server has the option to perform all HTTP authentication in user mode rather than have the web server attempt to do Kerberos/Negotiate authentication. This is required to get SSO working for the Gateway(s) running behind a load balancer.
To enable this feature, Open the web interface and go to Mobile Access -> Gateway Servers, click the Edit option in the cluster group, go to Advanced and enable the checkbox "Perform Negotiate/Kerberos authentication in user-mode"
Enabling Network Nodes
In order to be able to access Network nodes in the Web, while using SSO, several changes will be required. Since the Gateway Servers are running behind a load balancer, registering with Kerberos will need to happen with a user account, not computer name.
For this to work, the gateway services will need to run under a user account. You can either use the same LDAP user under which the Files Advanced server is registered, or you can select a new one, dedicated to your Gateway services.
Either way, the user you choose will need to be given the right to act as part of the operating system on the machines where the Gateway Servers are installed.
Selecting a user to act as part of the operating system
Running the Gateway Server's service as the selected user account
Once you have added the user you will be running the service as, you must set the Gateway service to run as them. To do so, complete the following steps:
Configuring the SPNs for the Gateway Cluster
In order for the Key Distribution Center Kerberos server to be able to authenticate users to the gateway cluster, each Gateway Server and the load balancer for the Gateways must be registered with the KDC server by running setspn and specifying the account name as which the service will be running as.
setspn -s HTTP/computername.domain.com username
For example, if you gateway service is running as user john, the command will be:
setspn -s HTTP/gatewayserver1.acme.com john
setspn -s HTTP/gatewayserver1.acme.com:444 john
setspn -s HTTP/gwloadbalancerdns.acme.com john