SQL Server Encryption - SQL Server Encryption - Technical Requirements Overview for New Installations and Upgrades - Foundation 24.1 - Foundation 24.1 - Ready - OnBase - Premier - external - Standard - Essential - Premier - Standard - Essential - OnBase/Technical-Requirements-Overview-for-New-Installations-and-Upgrades/Foundation-24.1/Technical-Requirements-Overview-for-New-Installations-and-Upgrades/Part-3-Databases/ADO.NET-Connection-Strings/SQL-Server-Encryption - 2025-12-04

Technical Requirements Overview for New Installations and Upgrades

Platform
OnBase
Product
Technical Requirements Overview for New Installations and Upgrades
Release
Foundation 24.1
License
Premier
Standard
Essential
ft:locale
en-US

Beginning in OnBase Foundation 24.1, any ADO.NET connection strings for Microsoft SQL Server databases enforce encryption by default. If you are upgrading from a previous version of OnBase, you must ensure the encryption settings for both your database server and your ADO.NET connection strings are compatible. For example, when using a SQL Server database, the connectionString element in your Application Server's web.config file must use either the Encrypt=Mandatory (default) string token to only allow encrypted connections to the database server or the Encrypt=Optional string token to allow unencrypted connections. These string tokens correspond to the older Encrypt=True or Encrypt=Yes tokens and the older Encrypt=False or Encrypt=No tokens used in previous versions of OnBase, respectively.

For more information on configuring ADO.NET connection strings, see the Application Server documentation.