Troubleshooting
This page is not available in the language you requested. You have been redirected to the English version of the page.
Link to this page copied to clipboard
Not for use with personal data
Troubleshooting
Common SCIM errors, what they mean, and how to resolve them. Errors raised by the SCIM resource handlers return a response in this form:
{
"schemas": ["urn:ietf:params:scim:api:messages:2.0:Error"],
"detail": "<message>",
"status": <code>
}Errors and resolutions
| Error message | Status | Cause | Resolution |
|---|---|---|---|
Subscription required |
402 | Your enterprise does not have an active SCIM subscription. Returned in the generic error envelope, not the SCIM error schema. | Contact your Deque representative to add the SCIM subscription. |
Invalid API key |
401 | The API key is incorrect or has been revoked. Returned in the generic error envelope, not the SCIM error schema. | Verify the key, or generate a new one in the axe Account Portal. |
Either authentication was not provided... |
401 | No API key was sent. Returned in the generic error envelope, not the SCIM error schema. | Add the X-API-Key or Authorization header. |
User email domain does not match enterprise root group |
400 | The user's email domain does not match the domain configured for your enterprise. | Confirm you are using the correct enterprise / API key, and that the user's email domain matches. |
Enterprise does not have an identity provider configured |
400 | Creating a new user, but SSO is not configured for your domain. | Configure SSO for your organization, or confirm the user already exists in axe. |
User is already a member of an enterprise |
409 | The user already belongs to another enterprise. | Use a different user, or deprovision the user from the other enterprise first. |
The group was not created because some users are not members of the enterprise. User IDs: ... |
400 | POST /Groups named a user who is not a member of your enterprise. |
Provision the user into the enterprise (create the user) before adding them to a group. |
Some users were not added to the group because they are not members of the enterprise. User IDs: ... |
400 | PATCH /Groups/{id} referenced a user who is not a member of your enterprise. |
Provision the user into the enterprise (create the user) before adding them to a group. |
Enterprise subscription out of seats |
402 | The product subscription has no available seats. | Free up a seat or contact your Deque representative to add seats. |
Count must be between 1-100 |
400 | A GET /Users request used a count outside the allowed range. |
Use a count value between 1 and 100. |
Cannot remove the last admin from the enterprise |
400 | Attempted to deprovision the only enterprise admin. | Assign another enterprise admin before removing this user. |
Group not found |
404 | The group ID does not match a subscription or team. | Verify the group ID from GET /Groups. |
Method not allowed |
405 | Used PUT on a group. |
Use PATCH to modify group membership. |
note
If your connector's test connection or schema discovery fails even though authentication is correct, enable "Non-Compliant Server" (or "relaxed") mode in your connector. axe supports the /Users and /Groups endpoints required for provisioning; this option skips full schema discovery. See Configuring Your Identity Provider.
Users are provisioned but cannot use a product
Confirm both conditions are met:
- The user has a product seat — they are a member of the product's subscription group.
- For products that use teams (such as axe Monitor), the user is on a team, and that team has been given access within the product.
See Limitations & Considerations.
Still stuck?
Contact your Deque representative or Deque Support with:
- The request (method, endpoint, and body — with secrets removed)
- The full error response
- Your enterprise name and identity provider