Hi Daniel,

I still see both options on LF 10 Web Access?

How have you got it configured?

Thanks Chris for this info.

I have pushed further my testing and I am finding out that on a system where I have upgraded from WebAccess 9 to 10, the Windows Authentication checkbox will show up but when performing a clean system installation, the checkbox will not show up.

I think there is an issue here and I will open a support case.

The behavior Daniel described is an SCR. The SCR for reference is 139433.
The workaround is to manually type in the windows login information in the <domain>\username format.

Note that WA will support using both a pre-set domain AND repository trustees in WA10 sp1, so you can set it up such that users don't have to type in their domain (just their windows account), while still allowing repository trustees. 

As for the checkboxes themsevles, they are no longer in the UI, but can be manually configured in the config file. That's simply to match other authentication updates happening in the suite, most notably the additional of LFDS SSO. 

Thanks Justin for this additional info.

I see now that you are trying to implement the same as what's been done in the Forms.

I have however a concern about this approach where the Laserfiche system will try to determine if it's going to log you in using AD authentication or Laserfiche Thrustee, depending on who's login will be valid.  In a production, there are not much chance to have two identical login (Domain like "DOMAIN\drouleau" and Laserfiche like "drouleau") but, personnally, I better like seeing that checkbox and decide if its a Windows Authentication or Laserfiche thrustee login.

To me, it makes more sense to leave that checkbox there.

We'll have some steps in place to cover scenarios where the same name is present (perhaps by adding a \ in front of the name or otherwise providing a way to indicate it) but, as you note, we're not too concerned about that in an actual production scenario. 

We'll look into why the checkbox isn't showing up, since the intent is that if people manually configure it, ok, sure, we'll show it, even if we're trying to discourage it. We'd prefer people to use LFDS SSO for integrated windows authentication rather than Kerberos, but obviously that option isn't avaliable to everyone. 

Hello,

The steps to fix there were not mentioned in this Answers post. Please provide that information. Also, Does LF intend to add this back as a simple check box in the configuration instead of a web file fix that will need to be changed after each upgrade/migration?

Regards,