asked on March 22, 2023 • Show version history

We have a client (self-hosted) receiving the following LFDS error:
"The security token is not renewable"

This is an error that they have not run into until a few weeks ago, coinciding with a Database / DNS related service outage.

The error message happens when users are logged into both Forms and the LF Web client interface. After an undetermined amount of time, the users will return to one browser tab or the other and the error will already be on the page. 

 

It doesn't kick them out of all sessions - just one web application or the other (Maybe Forms only?).

Signing back in works for a short while before the same thing repeats. No reports from those users that only work within a single application. Mostly related to people that do work in both Forms/Repo web apps. 

Potential correlation with recent incident related to a previous DB server hostname DNS record missing. The "old" record was pointing to the new centralized SQL Server that has been running for months in production. The decision was made during the previous db migration to leave connection strings in place and simply point old hostname to new shared DB host.  

This old missing DNS record created a service outage, during which time the team was prompted on LFDS (localhost) to re-connect LFDS to a licensing site. They did so successfully, but they did so using the new production DB server hostname, with the same DB credentials. This allowed them to access the LFDS interface and that's when they realized the old DB DNS record was missing. 

Note: The LFDS interface is still displaying the previous "old" connection string. Even though the UI had prompted them to re-attach initially with the updated and correct database hostname. 

Product versions:

  • Laserfiche Directory Server 11 (Build 11.0.2204.1467)
  • Laserfiche Web Client 11 (11.0.2109.7)
  • Laserfiche Repository Access 11.0.2102.205

  • Laserfiche Forms Professional Version 11.0.2212.30987


Event Log errors that seems to correlate with 'security token' error:
 

.



Thank you for any advice you can provide to help us track down and remediate this issue!

1 0