Note2Self

After the release of K2 1370, there have been some small updates to the K2HostServer.config file for your SmartObject Services configuration.

The basics is pretty simple, KB1370 added the ability to change binding and binding configuration on the REST and WCF endpoints separately. Because the binding configuration also defines the authentication mechanism, this means that REST endpoints could use basicHttpBinding with Basic authentication, while the WCF endpoint uses wsHttpBinding with Windows authentication. It also allows us to run either one endpoint on HTTPS while the other is not.

In my previous post on the K2 Services I showed you how to create a static endpoint, this simplifies the URL and allows you to rename or update the SMO without the endpoint changing. The configuration sections shown in those posts are now outdated and won’t work anymore. Since the KB article describing the change doesn’t have all the parameters, this post is also a note-to-self.

Yesteday I tweeted about inline functions and how to get your Icon working properly. Appart from all the info in Johnny’s blogpost, there are some other catches as well. Just because i keep forgetting them, here’s a mental note to myself. It’s a normal class library Start your project with a normal .NET class library. Make sure it’s .NET 3.5. Add references to the following files: SourceCode.Framework SourceCode.Workflow.Functions – this one isn’t always needed.

I’ve just “upgraded” to MSIE 9.0 within the Virtual Machine i use. Within that VM’s, I use a lot of Integrated Authentication, and my sites didn’t authenticate properly anymore. As it turns out, for integrated authentication to work, i had to put my sites in Intranet zone, not in the trusted zone. Having changed that, everything works fine again.