HTTP/SSL Conversion

 Browsers and support for HTTP have been diminishing, usually moving to HTTPS would be recommended.  Furthermore, later version of K2 (5.5) will only support HTTPS/SSL so conversion will be necessary.

You can reconfigure K2 to use HTTPS by using the Setup Manager.  At a high level:

- provision trusted SSL certificate, add to K2 server, reconfigure K2 site bindings for SSL/HTTPS

- Run the K2 Blackpearl and K2 Smartforms Setup Managers and configure the sites to use HTTPS as the default

- If K2 five, K2 Five Setup Manager

- If still using SmartObject services, you may have to convert it to HTTPS as per below, as the HTTP/HTTPS scheme when making a request from client to server will usually have to match:

https://help.nintex.com/en-US/k2blackpearl/DevRef/4.7/default.htm#Windows_Authentication_with_SSL_for_K2_SmartObject_Services.html

- If still using K2services subsite to start workflow, you may need to also make web.config changes to enable HTTP/SSL as per:

https://help.nintex.com/en-US/k2five/devref/5.2/default.htm#Reference/Services/Config/Configure-SSL.html

If on K2 5.5, using the workflow REST API and SmartObject Odata API would be recommended over legacy SmartObjectServices and K2services REST API:

https://help.nintex.com/en-US/k2five/userguide/current/default.htm#K2-Management-Site/Integration/Workflow-REST-API.htm

https://help.nintex.com/en-US/k2five/userguide/current/default.htm#K2-Management-Site/Integration/SmartObjectODataService.htm

https://help.nintex.com/en-US/k2five/devref/current/default.htm#Runtime/WF-REST-API/Workflow-REST-API-Samples.htm

https://help.nintex.com/en-US/k2five/devref/current/default.htm#Runtime/SmO-OData/SmO-OData-service.htm

Or if on premise, using the K2 assemblies:

https://help.nintex.com/en-US/k2five/devref/current/default.htm#Runtime/WF-Client/WF-ClientAPI.htm

https://help.nintex.com/en-US/k2five/devref/current/default.htm#Runtime/SmO-Client/ClientIntro.htm

Comments

Post a Comment

Popular posts from this blog

Blocking Error during K2 5.6 Server migration

  Error Encountered: Error during K2 5.6 migration to a new machine, keeping the SQL server unchanged. Error message:                       20:49:59:>> Certificates.FindCertificate: Found 1 certificates                       20:49:59:>> RegisterShard.Execute: Adding additonal connection string parameters to config service shard                       20:49:59:>> AdditionalConnectionStringParameters.AmendSQLConnectionString: Additional connection string parameter value: empty                       20:49:59:>> AdditionalConnectionStringParameters.AmendSQLConnectionString: Additional ConnectionString Parameters is empty                       20:50:04:>> AnalyzableAction.PopulateValidate...
Read more

Client Credentials flow with K2 Cloud with Odata, Workflow REST or SCIM

Image
This guide outlines the steps to using the Client Credentials Flow for accessing Nintex K2 Cloud's OData, Workflow REST, or SCIM APIs. Before you begin: Ensure your environment is eligible for Client Credentials Flow by contacting Nintex support ( https://customer.nintex.com/cases/Pages/default.aspx ). Have a SHA256 hash of the client secret of your choosing ready. Steps: Onboarding: Open a support ticket with Nintex requesting the onboarding of the Client Credentials Flow for your environment. Provide the SHA256 hash of your the client secret. https://help.nintex.com/en-US/k2cloud/userguide/current/Content/IdProviders/ClientCredentials.htm You can Generate the secret hash from a Client Secret value in a .NET console application. The onboarding team does not need the actual secret value, only the hash of it. Use the following steps and code example to generate the hash: Add the  IdentityModel  NuGet package. Add the  IdentityModel  library reference in the ...
Read more

Blocking error RegisterServiceInstanceObjects when upgrading to K2 5.6/5.7

K2 5.7 Upgrade Error: Blocking Issue with Orphaned Service Instances Error Message:             07:30:39:>> AuthorizationBase.RegisterServiceInstanceObjects: Current ServiceType and ServiceInstance details: ServiceType.Guid = GUIDValue1. ServiceInstance.Guid = GUIDValue2 . ServiceInstance.Name = ServiceInstanceName             07:30:39:>> ConnectionHelper.GetServerInstance: Create 'AuthorizationClient' instance using ConnectionContext             07:30:39:>> AuthorizationBase.RegisterObject: Validate Parent             07:30:39:>> AuthorizationBase.Execute: Logged Error: Failed: System.Exception: Item 'GUIDValue1' does not exist    at SourceCode.Install.Package.Actions.Authorization.AuthorizationBase.RegisterObject(String name, Guid id, Guid parentID, Guid classID, String className, Boolean inherit, Boolean propagate, IIdentityReferenc...
Read more