Question

Version 12 "2025 H2" Bug with LFDS?

Directory Server Version 12

Updated November 14

asked on November 7 • Show version history

v12 2025 H2 seems to have a bug in it. My users now have to reattach the repository every time they need to go into it. It does NOT retain the setting to use LFDS for SSO. Changing the registry does NOT set this as default.

We have many unhappy campers. If this is a bug, I need to know an estimated timeline for bugfix if possible.

Can anyone else reproduce this on their end? If so, and you use SSO, beware this update!

4 0

Answer

APPROVED ANSWER

replied on November 10

This was identified as a defect in Laserfiche Directory Server. Reference ID #622665. We're looking into a fix.

6 0

replied on November 13

Hi Miruna-

What configuration leads to this? Is it LFDS 12 and Desktop Client 12 using LFDS login (as opposed to Win Auth)?

0 0

replied on November 14

So far, it seems to be an issue with the HTML page that we embed for LFDS login, but i haven't gotten a full root cause explanation from the team. We'll be issuing an update to LFDS later this month for it.

4 0

Replies

replied on November 10

We're seeing this too. What would be great is if LFDS was always an authentication option in the desktop client - not just Windows Auth and Username/Password. When the full client does its look/check/whatever to see if LFDS is an option appears to be when we run into problems.

5 0

replied on November 7

We have the same issue.

4 0

replied on November 7

Hi Chris,

That certainly sounds frustrating. Could you please have your Solution Provider open a support case with us so we can investigate? Have them reference this Answers post so they can see at least one other customer is affected.

If a bug, this is likely in the Repository Windows Client about how it retains settings, not Directory Server itself. Please make sure to provide the exact version numbers of Repository Windows Client, Repository Server, and Directory Server when you/your SP open the case.

Thanks,
Sam

2 0

replied on November 10

Thanks Sam! Done!

They can still use Web Client, but they loath it ha ha. Not an emergency since work can continue. Just some restless natives.

2 0

replied on November 13

I am planning to upgrade from 11 to 12, and i believe we will be going to spring version first. Is this your initial upgrade or were you on the spring version without issue for a while?

0 0

replied on November 13 • Show version history

We did spring first. It was fine. We wanted the additional features from the fall release and it was listed as a minor update. So we took the chance. That was our decision and we own it. Our users can still work, so we don't feel entirely bad that their only consequence is to have to attach the repo every time they go into the desktop client OR use web client. Secretly, we want them to stop using desktop client so much and get used to web client ha ha.

We did LFDS first and let the legacy versions interact with it for a month or so, then we upgraded to version 12 Forms, LFS. The WF designer throws errors if not version 12 so that is really what should be the priority. Do WF server first after LFDS.

0 0

You are not allowed to follow up in this post.

Question

Question

Version 12 "2025 H2" Bug with LFDS?

Answer

Replies

Sign in to reply to this post.