First, out of the box web services for your most common K2 client API tasks.  Here’s a link to the help file that describes the interfaces in more detail: K2 Web Services

Next, for reasons including but not limited to those that K2 cites here, it is an exciting development that the 1290 release of K2 will include a secondary pass-through authentication mechanism.  It has its limitations and the whitepaper is definitely worth a read, but below is a excerpt to wet your appetite on this much needed feature.

“Kerberos is and will remain the recommended and preferred technology for handling distributed user security for the K2 platform. However, for many customers, the configuration and use of Kerberos is not a reasonable expectation. This may be for a number of reasons, such as the following:

  • Lack of internal skill, often the case in small or specialized companies.
  • Limited access to skill, perhaps due to infrastructure outsourcing agreements.
  • No access to Active Directory to make the required changes (such as in a Proof of Concept/Demo).
  • Time constraints for delivery, making infrastructure configuration delays severely problematic.
  • Basic business requirements (such as a simple internal document approval) that just don’t warrant time and expenditure on advanced security configuration.

To address this need K2 has implemented a technology to allow Kerberos dependencies to be removed…” – K2 KB001226