Summary

Laserfiche Directory Server 11 Update 3 (11.0.2303.1978) includes the following changes:

• Support for synchronization of Azure AD users using SCIM 2.0, including user creation, email updates, licensing, and disabling unauthorized users.

Additional Changes

• The Endpoint Configuration Utility was renamed to "Laserfiche Directory Server Configuration Utility", and now supports a "debug" mode by running 'XmlEndpointUtility.exe /debug' from the command line.
• STS Site event auditing (the creation/modification/deletion of STS sites under database settings) now appears in the audit report.
• Added support for configuring the SQL connection pool size limit. Set the limit by adding an appSettings key in "C:\Program Files\Laserfiche\Directory Server\LFDS.exe.config" and saving the file and restarting the Laserfiche Directory Server service. For example,

  <add key="ConnectionPoolMaxPoolSize" value="1000"/>

  The default .NET ConnectionPoolMaxPoolSize is 100. There is no need to change the default value unless you encounter error messages that indicate LFDS is hitting the max pool size. To date, Laserfiche has only received reports of this issue from customers with tens of thousands of users, mostly in Education. The issue is mostly likely to occur during peak login activity periods with many (thousands) of users. These error messages will say "System.InvalidOperationException: Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached. at System.Data.SqlClient.SqlConnectionPoolManager.GetPooledConnection(SqlConnectionString options, Boolean& isInTransaction) at System.Data.SqlClient.SqlConnection.Open()" or similar. If you encounter a max pool size error, there are two recommended general approaches to increasing it.
  • For systems with under 2,000 peak active users: Start by setting the ConnectionPoolMaxPoolSize to "200", double the default value. If the issue still occurs, either increase the max pool size by another 100 or double it. Repeat until the issue no longer occurs.
  • For systems with over 2,000 peak active users: Start by setting the ConnectionPoolMaxPoolSize to "1000". If the issue still occurs, increase the max pool size in increments of 100-500, with larger increases the more frequently the issue occurs.
  • Once the issue no longer occurs, at peak activity times run the SQL Server "sp_who" built-in stored procedure to see how many connections are open to the Directory Server database. Once a few "sp_who" data points are available, if the configured max pool size is significantly above the maximum actual connections (e.g., MaxPoolSize=1000, observed max = 300), consider lowering the max pool size to the observed max plus a buffer (+100 or so). If you are concerned about potential activity peaks that may be significantly higher than observed, for example an upcoming "Open Enrollment" week for a large school district where tens of thousands of users would suddenly be active, use a larger buffer.
  • For more information on SQL Server Connection Pooling, please see Microsoft's documentation: SQL Server connection pooling (ADO.NET)
• Microsoft Windows 8.1 is no longer a supported operating system for Laserfiche Directory Server.

Fixes

• URI fragment identifiers (queries after #) are now not discarded when signing in with SAML. (362671)
• The "MFA status" value in the audit reporter now matches the MFA status values of "Inherited", "Required", or "Not Required". (367935)
• Improved the STS login page for better screen reader support. (382494)
• Moved the "Register directory users" button to the left side of the user creation page. (390022)

More Information

Laserfiche Directory Server Update 3 is included as part of the Laserfiche 11 installation package.

Download the Laserfiche 11 package for the latest updates.

Related Links

1014444 Release Notes for Directory Server 11 Update 3