Subscribe to Help Center RSS FeedThis article helps you troubleshoot common issues when configuring custom SCIM connectors. For more information on configuration, see Identity Management using a Custom SCIM Integration.
This typically indicates that JumpCloud is expecting one data type and the service provider is sending another data type. Contact the service provider to troubleshoot further. JumpCloud implementation follows the SCIM schema standard. Per section 2.2, if the data type is not specifically stated, we use the data type of "string."
The service provider is sending the id as an integer. We only support the id as type string in adherence with the SCIM schema definition. You will need to contact the service provider to determine if they can also send that value as a string.
- Remove the trailing ‘/’ from the Base URL value. The value should be https://miro.com/api/v1/scim
- Turn Off the Enable management of User Groups and Group Membership in this application option. Miro currently only supports “Group Updates”. JumpCloud is currently only able to support a custom SCIM integration with service providers that support Group Creation, Group Updates, and Group Deletion
Disable Enable management of User Groups and Group Membership in this application option. JumpCloud currently requires Group Creation, Group Updates, and Group Deletion to enable group management for a service provider. Databricks does not support Group Updates.
The Service Provider does not support groups. Disable Enable management of User Groups and Group Membership in this application option and try and activate again.
