Symptoms

When using the ServiceAccount or Impersonate AuthenticationModes when registering a CRM service instance, registration throws an error message regarding Validation of certain components. However, using Static AuthenticationMode while specifying CRM Admin credentials, this properly registers the service instance and brings back the proper schema.
 

Diagnoses

This has been identified to because the CRM Service Broker is not claims-aware. CRM expects a claim or certain information to be able to create a claim for the incoming user, but these items are not sent when using the ServiceAccount or Impersonation AuthenticationModes.
 

Resolution

The following Feature Request was created to remedy the behavior in a future release:

Feature 582335: K2Blackpearl CRMIntegration: Feature request to make CRM Claims aware to be able to register an instance using ServiceAccount or Impersonate

The current workaround is to use Static Authentication mode with the correct user account with CRM admin privileges to be supplied. This feature is not currently slated for a release as of yet.