Skip to main content
Nintex Community Menu Bar
Question

Facing the Issue while connecting to the Workflow API and SmartObject API

  • June 30, 2026
  • 5 replies
  • 38 views

Forum|alt.badge.img+2

Hi Team,

I enabled the Workflow and SmartObject API in the k2 management. K2 is hosted in the Windows 2025 VM and installed version is K2 Five 5.8 . I am able to connect to the API while i am debugging the application locally. I am not able to connect to the API while deployed to my QA Environment.

I validated in the K2 server registry TLS 1.2 is enabled. In the .net framework code i am taking care of the TLS 1.2 protocol

foreach (SecurityProtocolType protocol in Enum.GetValues(typeof(SecurityProtocolType)))
            {
                if (protocol.GetHashCode() == 3072)
                {
                    platformSupportsTls12 = true;
                }
            }
            // enable Tls12, if possible
            if (!ServicePointManager.SecurityProtocol.HasFlag((SecurityProtocolType)3072))
            {
                if (platformSupportsTls12)
                {
                    //Console.WriteLine("Platform supports Tls12, but it is not enabled. Enabling it now.");
                    ServicePointManager.SecurityProtocol |= (SecurityProtocolType)3072;
                }
             }

I am getting the below issue while getting smartObject.

Error getting case workflow - Exception: [System.Exception: GetSmartObjectData ---> System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Authentication failed because the remote party has closed the transport stream.
   at System.Net.TlsStream.EndWrite(IAsyncResult asyncResult)
   at System.Net.ConnectStream.WriteHeadersCallback(IAsyncResult ar)
   --- End of inner exception stack trace ---
   at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
   at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)
   --- End of inner exception stack trace ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult()

Please help me on this if anyone faced the similar issue or any thing i am missing.

5 replies

Forum|alt.badge.img+7
  • Nintex Partner
  • July 1, 2026

Hi,

I can't quite figure out what your sample code does, but since you're dealing with TLS settings, take a look at the following article and the registry keys that affect them.

K2 and TLS 1.2 & 1.3 Support

I usually set the minimum requirements in environments, and then I don't have any problems.


MillaZ
Nintex Employee
Forum|alt.badge.img+23
  • Nintex Employee
  • July 6, 2026

Hi ​@Karthik503 have you resolved this issue? 


Forum|alt.badge.img+2
  • Author
  • Rookie
  • July 6, 2026

 I followed the documentation to update the Hkeys in the Registry. Still facing the issue.


MillaZ
Nintex Employee
Forum|alt.badge.img+23
  • Nintex Employee
  • July 7, 2026

Hi ​@Karthik503 perhaps in this case it would be best to log a support ticket.


Forum|alt.badge.img+11
  • Nintex Employee
  • July 7, 2026

Are you also using a trusted certificate?  Using a self-signed/untrusted certificate may work on the machine that it is on (or if it was added to trusted root authority) but may not work on a client where it isn’t trusted.  Using a public or internal CA trusted certificate is recommended.