You are viewing limited content. For full access, please sign in.

Question

Question

Possible Bug: Snapshot Authentication

asked on January 30 Show version history

Using Snapshot 12.0.2508.942, every Snapshot user we have reports that they are being prompted to login every time they attempt to print. We are using LFDS with TLS enabled. The configured server name reverts from the FQDN (lfserver.foo.com) to just the server name (lfserver) after updating the config, closing the config app, and reopening the config app. I've tried running the config as the user, running the config as admin, saving over the default user profile, saving over the default system profile, and none of these fixed the issue.

I've edited the following registry keys, hoping that would fix this issue:

HKEY_USERS\<Affected SID>\Software\Laserfiche\Snapshot8\Profile\CurrentUser
"Server"="lfserver.foo.com"

HKEY_CURRENT_USER\Software\Laserfiche\Snapshot8\Profile\CurrentUser
"Server"="lfserver.foo.com"

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Laserfiche\Snapshot8\Profile\CurrentUser
"Server"="lfserver.foo.com"

I believe that this workaround fixed it; I am still monitoring to see. Is this an issue with my installation/environment, or is this a bug? Is there a fix?

0 0

Replies

replied on February 2

Hi Kevin,

To determine the specific reason why you're having to modify the Snapshot profiles manually through the registry, please open a support case. We can gather more information about the installation environment to narrow down some possible causes.

1 0
replied on February 2

Please provide your Directory Server (and STS, if using any standalone STS instances) build number with the case. Laserfiche Snapshot uses the "embedded" LFDS login page, and the Dec 2, 2026 patch update for Directory Server includes two potentially related fixes:

  • Directory Server (12.0.2511.289)
  • Directory server STS (12.0.2511.160)

 

  • Fixed an issue that could hide the "Laserfiche Directory Server" option in the repository desktop client's sign in page. (622665)
  • Fixed an issue where the STS did not properly handle EmbeddedPostbackWhitelist URLs. (623255)
1 0
You are not allowed to follow up in this post.

Sign in to reply to this post.