Thank you Chase.  I did see that post and the customer tried it.  It is still prompting them.   Any other ideas?

Just to double check, they tried adding and/or editing both of these keys?

HKEY_CURRENT_USER\Software\Laserfiche\Client8\Profile\MyRepositoryNameSettings\LFDSSTSUrl

HKEY_CURRENT_USER\Software\Laserfiche\Client8\Profile\Settings

(Where "MyRepositoryName" is replaced with your actual repo name.)

Chase,

That is correct.  We added both of these keys onto a machine the window client was installed on.

We utilize SAML for our MFA and have been able to find all the configurations to allow logging in on all web client applications.  However, this is the last piece we cannot find. During a clean install it is still placing the ".ad" in the Directory Server Address.  We can either change the registry keys for each machine (which is a work-around), or we can change it every time we log into the client.  Is there somewhere else we have missed that needs updated for the LFDS authenication to occur without this step every time? Thank you!

Hi Emilee,

Sorry to ask for more clarification, but I notice you mentioned "We can either change the registry keys for each machine (which is a work-around)". Do you mean that adding the keys does in fact work, but you don't want to alter the keys on every client machine? If this is the case, I recommend you push out these keys with a group policy to all the client machines so you don't have to do so by hand. I believe this is the expected solution to alter the default on a wide scale. If I'm mistaken and the registry keys don't seem to be changing anything, we can loop in someone from the client team for input.