Nintex Ideas

đź‘‹ Use this site to provide feedback and ideas for all Nintex Products. See our post on Nintex Community "Welcome to Nintex Ideas" for more details on Nintex Ideas, how an idea is handled by our product teams and more!


If you have questions about Nintex Ideas, please contact ideas@nintex.com

If you require support, please visit Nintex Customer Central

If you have a sales inquiry, please contact sales@nintex.com

Add a new idea Subscribe
Workspace Nintex Automation On-Prem (formerly K2 Five)
Categories Security
Created by Tin Bui
Created on Feb 27, 2025

RELATED IDEAS

Installing K2 with trusted certificates instead of self-signed

K2 typically installs self-signed certificates for internal use by its services, which is generally acceptable for most customers. However, self-signed certificates violate "CAT II finding in IIS Site STIG" policy. During the installation process, it would be great if you could specify a trusted certificate that K2 can use for its internal services. These are separate certificates to the IIS binding certificate that is currently configurable.

image (2).png
image (2).png
  • Attach files
      Drop here to upload
    • Tin Bui
      Reply
      |       Mar 4, 2025

      Some official documentation detailing the internal certificates generated during the K2 installation process, including their purpose and the current limitation of not being able to specify or replace them with custom certificates would also be helpful.

      Certificates includes:

      * Environment Owner

      * K2 OAuth High Trust

      * K2 On Premise Root

      * “hostname.domain.topleveldomain” – issued by “K2 On Premise Root”

      * K2 STS Certificate

      * sourcecode-appit-apptemplates