Troubleshooting Single Sign On

• Desktop or Web client users must be on a separate machine from the one running the Files Advanced server (but in the domain) or SSO will not work.
• You must access the server using the exact same FQDN as the SPN is using; e.g., https://ahsoka.acme.com . You cannot use other DNS names or IP addresses e.g., https://localhost or https://10.20.56.33.
• Verify that you can log in to the Files Advanced server without using SSO by entering the exact same LDAP credentials as your client windows machine uses. This will verify that your account credentials are valid for Files Advanced regardless of SSO configurations.
• Verify that you can access all Data sources without using SSO and using the same credentials as your LDAP login account.
• If you are unable to log in via SSO, double-check that you have configured your Web browser for SSO to the FQDN to which you are connecting, and you are logged in on your client machine using a domain account.
• Single Sign-On will not work if the Files Advanced Server is running on the Domain Controller.
• Files Advanced will not work with SSO if you are trying to access it from the machine that is the Domain Controller.

  Note: Due to how Kerberos works, you cannot authenticate via SSO from a client application or Web browser running on the Domain Controller or the Files Advanced server.

  Additionally, the Files Advanced server cannot authenticate to the Domain Controller when the Files Advanced server is running on the Domain Controller.

• If you get a 401 Error when trying to log in using SSO, check the username and password in the web.xml file and make sure that any special characters are escaped properly. The special characters are: &, >, ", ' , or <, for information on how to escape them, please see step 5 of the Editing the web.xml file section.