Configuring K2 for SharePoint On-Premises SSL/non-SSL based scemas

  • 24 February 2022
  • 0 replies
  • 12 views
MillaZ
Userlevel 5
Badge +20
 

Configuring K2 for SharePoint On-Premises SSL/non-SSL based scemas

kbt130227

PRODUCT
K2 blackpearl 4.6.11 to 4.7
BASED ON
K2 blackpearl 4.6.11
SEE ALSO
 
TAGS
Troubleshooting Document
How to Document
This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice. This article is not considered official documentation for K2 software and is provided "as is" with no warranties.
LEGACY/ARCHIVED CONTENT
This article has been archived, and/or refers to legacy products, components or features. The content in this article is offered "as is" and will no longer be updated. Archived content is provided for reference purposes only. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.

Objective

This aritcle intended to clarify impact of existing K2 SSL requirements on configuration K2 for SharePoint in your environment.

 

Consider the following scenario: You are trying to configure K2 for SharePoint app after it has been deployed into SharePoint App Catalog (SharePoint 2013). But when clicking on the Settings link of the K2 for SharePoint app you are getting the following Error Message:

 

"The resource cannot be found. Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly. Requested URL: /mpadmin/K2forSharePoint/Pages/Settings.aspx"

 

This usually caused by the fact that app catalog was provisioned for HTTP web application (has HTTP URL) whereas your K2 schema is HTTPS (designer/runtime URLs) or the other way round. You have to configure your app catalog to match your K2 designer/runtime schema, keeping in mind that HTTP configuration requires extra configuration steps and recommended only for development environments.

 

For more details on how to configure HTTP web app and app catalog refer to the following section of K2 help: K2 FOR SHAREPOINT GETTING STARTED GUIDE 1.0 > Before You Begin and navigate to Sofrware and Hardware Requirements > SSL Requirements > Workaround for configuring a K2 for SharePoint On-Premises for non-SSL based connections

Before You Begin

If you doing your K2 for SharePoint installation for the first time consider reading K2 FOR SHAREPOINT GETTING STARTED GUIDE before you begin installation and configuration process.

How-to Steps

As stated in K2 FOR SHAREPOINT GETTING STARTED GUIDE 1.0 > Before You Begin section of K2 documentation under Sofrware and Hardware Requirements > SSL Requirements > Supported Scheme Configurations:

 

The URLs between your SharePoint site and your SmartForms and View Flow sites should be the same - either all SSL or all non-SSL.

We only recommend HTTP for development environments and if you want to use HTTP for web catalog you also have to use HTTP for K2 (designer/runtime URLs) - again if you open link mentioned above and look at Software and Hardware Requirements > Supported Scheme Configurations you will see a table which says that we do support

only: HTTP SharePoint + HTTP K2 Designer or HTTPS SharePoint + HTTPS K2 Designer and for HTTP option you also have to follow extra steps described under "Workaround for configuring a K2 for SharePoint On-Premises for non-SSL based connections" on the same page.

We highly recommend that you use the default SSL based connections, however, we realize that this is not always possible due to other constraints. This workaround provides steps for configuring the K2 environment for HTTP to HTTP connections in a K2 for SharePoint On-Premises installation.
Check out these Nintex University Learning paths: https://community.nintex.com/p/NintexUniversity

0 replies

Be the first to reply!

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings