Forms 11 broke Windows Authentication

asked on September 13, 2022

We upgraded LFDS and Forms to 11 (From 10.4) this weekend because our VAR insisted that was what was causing our resources consumption issue which was crashing Forms multiple times a day. They troubleshot for over a month. Well after the upgrade we now have the same resource consumption issue as well as a new Windows Authentication issue. When you click on Windows Authentication it doesn't work. I've attached a picture of the error.

Anyways... I see a few posts about Windows Authentication being broken after the upgrade but no solutions. Has anyone successfully solved this issue or have any ideas we can use to troubleshoot? Our VAR clearly doesn't see it as a priority but our 5k+ customers that have to sign a Workers Comp Insurance Agreement before the 1st do. I appreciate everyone's support from this forum so thank you in advance.

Error Message.PNG (51.8 KB)

| Download

0 0

SELECTED ANSWER

replied on September 13, 2022

This is common if you use a DNS Alias name in the endpoint utilities:

C:\Program Files\Laserfiche\Directory Server\XMLEndpointUtility.exe
C:\Program Files\Laserfiche\Directory Server\Web\WebSTS\STSEndpointUtility.exe
C:\Program Files\Laserfiche\Laserfiche Forms\Forms\bin\EndpointUtility.exe

In these utilities, you must use the actual machine name (NetBIOS Name), rather then a DNS Alias. You can use the DNS Alias in the URLs and redirects, but the endpoints need to use the true machine name(s).

3 0

View 3 previous replies

replied on September 13, 2022

In the Endpoint Config Utility it says Fully qualified domain name(Host domain.com): We have the FQDN in there and it matches the same box in the STSE EnpointUtility. Are you saying this should be the NetBios name instead of the FQDN?

0 0

replied on September 13, 2022

It should be the value that is returned when you run this PowerShell command:

[System.Net.DNS]::GetHostEntry("localhost")

4 0

replied on September 13, 2022

Agree with Blake above. As an added note, it should be the results of running that command on the LFDS Server.

It does need to be the NetBios name in the FQDN format.

FQDN is kind of a misnomer, as that simply means the name needs to be fully-qualified (i.e. it needs to have the trailing "domain.top-level-domain")

Example:

My server's NetBios name is "LFServer.company.com".

I used another DNS name, in line with an SSL/TLS certificate for the URLs; the only name I give users is "Laserfiche.mycompany.gov".

Both "LFServer.company.com" & "Laserfiche.mycompany.gov" are FQDNs, but the one I have to use in the endpoint utilities is "LFServer.company.com", since that's the actual machine name (returned by the above PowerShell command, or looking in the System Properties on that server).

0 0

replied on September 13, 2022 • Show version history

Fixed. Thank you.

Anyone reading in the future run that command in elevated Powershell. Use that exact name for the FQDN in the Utilities.

1 0

replied on September 13, 2022

Can you give specifics as to what you did to fix the issue so someone else with the same issue reading this post will know?

0 0

replied on September 13, 2022

Just updated it. Thank you again.

0 0

Question

Question

Forms 11 broke Windows Authentication

Answer

Replies

Sign in to reply to this post.