TarunPatel2674

EndpointsWCF

We have been using K2 for a number of years.   We connect to our internal WCF services from workflow using smartobjects services (EndpointsWCF).  These services were http and now we are in the process of updating them to https.  The connection is made to the WCF but username (windows authentication is enabled in IIS for the WCF service) seems to be blank.

 

Are there any additional steps to be taken for Https?  The same works for Http...

 

 

0 Kudos
Reply
4 Replies
TinTex
Nintex Employee
Nintex Employee

Re: EndpointsWCF

I assume the service instance urls have also been updated to HTTPS?
0 Kudos
Reply
TarunPatel2674

Re: EndpointsWCF

Yes the service instance urls have been updated to HTTPS.
0 Kudos
Reply
TinTex
Nintex Employee
Nintex Employee

Re: EndpointsWCF

To further narrow down where the issue is, does it work outside of a workflow? Through the SMOTester tool, through K2 Management site, or a view?
0 Kudos
Reply
TarunPatel2674

Re: EndpointsWCF

Yes, the endpoint WSDL can be accessed via browser.  I also run it via WCFTestClient and works perfectly well.   The SMOTester also updates the services.   But when the WF tries to invoke, it comes up with:

 

ServerEvent: Message: Could not establish trust relationship for the SSL/TLS secure channel with authority 'trackerdev2016:9191'.; ServiceName: MatterWCFService; ServiceGuid: 7b0c04c0-89cd-4383-80cc-754655cd9ece; InnerExceptionMessage: ;

InnerException: Message: Could not establish trust relationship for the SSL/TLS secure channel with authority 'trackerdev2016:9191'.; ServiceName: MatterWCFService; ServiceGuid: 7b0c04c0-89cd-4383-80cc-754655cd9ece

 

0 Kudos
Reply