Question

Auto-Sign In Works with Localhost, but Not Server Name

Web Client Laserfiche Version 10 Administration

Updated February 19, 2018

asked on February 17, 2018

I am working with a client and enabling pass-through authentication for the web client. The web client server is installed on the same machine as the Laserfiche Server. In the web client configuration, the Connection option is set to 'Auto-sign in using integrated Windows authentication'.

If I browse to the web client using http://localhost/laserfiche, it will auto-sign the user in. If I browse to the web client using http://servername/laserfiche, it will not. Just to make sure it was not something weird with trying to browse to it using the server name from the same machine, I have tried it on 2 other machines as well with the same result of it not working.

Does anyone know why it is not working correctly, or what to check?

1 0

Answer

SELECTED ANSWER

replied on February 19, 2018

IE/Chrome or Firefox? (the links are from AWS documentation, but the same setup applies to all sites attempting to use single sign-on)

0 0

replied on February 19, 2018

Another possibility is that the browser is using NTLM for "localhost" and Kerberos for the real hostname. You can try removing the Kerberos option from the Windows authentication providers list for the application in IIS management.

0 0

Replies

replied on February 18, 2018

What do you mean by "not working"? Do you get an error? What behavior do you observe?

0 0

replied on February 18, 2018

I apologize. I should have been more clear. By not working, I mean it is prompting for credentials.

1 0

You are not allowed to follow up in this post.

Question

Question

Auto-Sign In Works with Localhost, but Not Server Name

Answer

Replies

Sign in to reply to this post.