What's New

• Enhancements to the installer were made to allow extra characters for license keys with expiration dates beyond 12/31/2022.
• This version of K2 Five implements authentication on the K2 Identity web application. For authentication to work seamlessly, the Identity web application must have the same claims configuration as your Runtime SmartForms realm. For details see the Multi-Authentication Providers.
  • If you manually configured K2 integration with AAD, you need to configure the Identity URI in Azure as a redirect URI. See the topic Step 2 - Create an App in AAD for your K2 site and gather information for information on how to do this.
• K2 Five (5.6) supports integration with Azure Government Cloud Computing (High Security) for the United States region. See the topic Integrating K2 Five and Azure Government Cloud Computing High Security(GCC) (High Security) for more information.

• K2 supports IPv4 and IPv6. K2 will operate as expected on environments where IPv6 is the only IP configuration.

• SQLUM has been enhanced to allow administrators to configure a lockout policy. In order to protect SQLUM users from brute force password guessing attacks, the lockout policy will lock a SQLUM user after the configured amount of invalid password attempts, for a configured amount of time. For more information see the SQLUM administration topic.

Administrators can create SQLUM users in a domain\username format (referred to here as the full username) even though SQLUM has no concept of a domain. Before K2 Five (5.6), users created with the domain\username format could log in using just the username portion if the K2 server is running in the same domain as the domain part of the full username. This behavior has changed and now in clean installations of K2 Five (5.6) and on the first upgrade to K2 Five (5.6) from a previous version, SQLUM users that were created with the domain\username format need to log in with the full username.

• Silverlite is not supported.

• The following dependencies are required. If the dependency is not installed, the Setup Manager will block installation and prompt you to download an install the dependency, then continue:
  • .NET Core Hosting and Runtime Bundle 6.0.1
  • Microsoft Visual C++ 2019 Redistributable
  See the compatibility matrix for all supported versions

If you manually configured K2 integration with AAD, you need to configure the Identity URI in Azure as a redirect URI. See the topic Step 2 - Create an App in AAD for your K2 site and gather information for information on how to do this.