We have been using K2 (Rev 4.6.4) in the context of SharePoint 2010 with Claims Authentication (AD FS), and have no problems.

We have a piece of code that runs just fine when used in a SharePoint 2010 application with Claims in use.

This same code also works just fine when used within a .Net application which doesn't use Claims authentication.

However, when I run that same code within a .Net (specifically MVC4) application which has Claims authentication in place, when the Conection.Open() is called, the application just hangs during the Open(), with no Exception generated, and no errors showing up in the K2 logs.

Sample code:

Connection connection = new Connection();

ConnectionSetup connectionSetup = new ConnectionSetup();

connectionSetup.ConnectionParametersm"Authenticate"] = "true";

connectionSetup.ConnectionParametersm"Host"] = hostname;

connectionSetup.ConnectionParametersm"Port"] = "5252";

connectionSetup.ConnectionParametersm"Integrated"] = "true";

connectionSetup.ConnectionParametersm"IsPrimaryLogin"] = "true";

connectionSetup.ConnectionParametersm"SecurityLabelName"] = "K2";

connectionSetup.ConnectionParametersm"WindowsDomain"] = domainname;

connectionSetup.ConnectionParametersm"UserId"] = userid;

connectionSetup.ConnectionParametersm"Password"] = password;

connection.Open(connectionSetup);

connection.Close();

So, what am I missing? What needs to be done in order to use the K2 API with custom .Net code in the context of a Claims Authentication application.

Thanks...