Client Configuration

This content applies to legacy components (such as K2 Studio and K2 for Visual Studio), legacy assemblies, legacy services or legacy functionality. If you have upgraded from K2 blackpearl 4.7 to K2 Five, these items may still be available in your environment. These legacy items may not be available in new installations of K2 Five. These legacy items may also not be available, supported, or behave as described, in future updates or versions of K2. Please see the legacy component support policy for more information about support for these components.

The default app.config file that gets created by Visual Studio when making a service reference to WCF endpoints will contain the same settings as found in the service web.config.  Since SyncWCF.svc is configured with a clientCredentialType="None" client calls to the service endpoint will use Anonymous and fail.  It is recommended that the clientCredentialType in the client side app.config be set to Basic or Windows depending on the desired authentication.

<binding name="BasicHttpBinding_ICoreService">
  <security mode="Transport">
    <transport clientCredentialType="Basic" />
  </security>
</binding>

Additionally, in a Kerberos distributed environment, it is necessary to include the Service Principal Name (SPN) setting in the app.config by including the following nodes for each  <client><endpoint> element.

<identity>
  <servicePrincipalName value="spn"/>
</identity>

 The value of the value attribute should be set to a valid client SPN to avoid unexpected behavior in future .NET framework releases.  See the .NET Framework Readme for more information: http://download.microsoft.com/download/a/2/8/a2807f78-c861-4b66-9b31-9205c3f22252/dotnet35sp1readme.htm - Section 2.3.2.2