Office Integration - Cannot Use Windows Auth as LFDS Auth is Configured

asked on January 6 • Show version history

Hi All,

We have a client using the Office integration to save documents from Word directly into the repository. The customer are using Windows Accounts in LFDS to license users. Those Windows Accounts are then granted access to the repository by adding them in the Windows Accounts node of the Admin Console.

All users then sign in to Laserfiche using the Windows Authentication option. For most users this seems fine, both using the Windows Client and Office Integration, they choose the Windows Authentication sign in option and it works.

However, one user can't sign in via the Office Integration as he gets the following error when trying to sign in using the Windows Authentication option. He can sign in via with Windows Client using WA fine.

Because your organization is using Laserfiche Directory Server authentication, you cannot use automatic Windows authentication. To log in using your windows account, type you user name and password, with your username in the format domain\username.

Does anyone know what this message means please? And why it's only showing for one user in the organisation? Just because the users are licensed through LFDS, it shouldn't stop them from signing in using Windows Authentication.

Kind regards,
Dan

0 0

SELECTED ANSWER

replied on January 6

Hi Dan,

I'd start by double checking the exact versions of the Laserfiche Windows Client, Laserfiche Office Integration, and Laserfiche WebTools Agent (if installed) for this user and compare to few known working ones.

Re:

Just because the users are licensed through LFDS, it shouldn't stop them from signing in using Windows Authentication.

It doesn't. Something else is going on. Note the error message mentions "Laserfiche Directory Server authentication", rather than licensing. Is this user perhaps trying to connect the Office Integration to the repository via a Laserfiche Web Client instance that has LFDS SSO enabled?

1 0

replied on January 7

Thanks Sam, you were right. It looks as if this user in particular had chosen the option to sign in using the Web Client URL, rather than the server name. He's detached the repository and attached it using the server name instead and all is working for him now. Thanks for your help!

1 0

Question

Question

Office Integration - Cannot Use Windows Auth as LFDS Auth is Configured

Answer

Replies

Sign in to reply to this post.