K2 Site Configuration

To ensure the K2 Site performs at its best it is essential to have the correct configuration setup. There are several factors and components within the product environment that requires specific or suggested configuration. This section provides configuration information for the following:

Configure	Description
Authentication	The K2 Site makes use of the Nintex K2 security mechanisms which are; Windows Authentication or Forms Authentication.
Manually Configure K2 for AAD	The product integrates with Microsoft Azure Active Directory (AAD) which allows AAD users to log in to the web sites and allows you to assign AAD users workflow tasks and get user details using the AAD SmartObjects.
Integrating the product and Azure Government Cloud Computing High Security(GCC)	The product can integrate with AAD, Exchange, and SharePoint Online in Azure Government Cloud (GCCH).
Secondary Runtime site	The default Runtime site uses Windows Authentication and authenticates to Active Directory. Should the need arise to grant certain users Anonymous Access rights and other users Windows or Forms Authentication rights, two runtime sites can be installed where one is configured for Anonymous Access and the other for Authenticated Access.
Upgrading Secondary Sites	It is possible to configure a single K2 site with multiple authentication providers. In the past if you required multiple authentication methods for your SmartForms sites you needed to create a copy of your SmartForms site for each authentication method.
Selecting Role Services on IIS Server	When K2 Site is installed in a distributed environment where the Designer and Runtime components are installed on different IIS servers, certain Role Services must be enabled on the Runtime server.
IIS Server response header	Prevent IIS Server version information disclosure through the K2 Site Server response header by configure a URL Rewrite rule that that will remove or change the value.
Enabling secure cookies for K2 sites	We recommend that you use SSL (HTTPS) when configuring sites (Viewflow, Designer, and SmartForms Runtime sites). If you don't use SSL you run the risk of unencrypted site traffic being intercepted.