JumpCloud Provisioning Error "Bad Request. Errors reported by remote server: addresses.0.type in body is required"
Dec 29, 2025
Okta Classic Engine
Okta Identity Engine
Okta Integration Network
Overview
JumpCloud provisioning flow fails with the following error, visible in the Okta dashboard:
Automatic provisioning of user <username> to app JumpCloud failed: Error while creating user <username>: Bad Request. Errors reported by remote server: addresses.0.type in body is required
Applies To
- JumpCloud
- Provisioning
- Error
Cause
JumpCloud SCIM server returned this error because the User provisioning request does not have the Address Type attribute value.
Solution
- JumpCloud is expecting a value for the Address Type attribute value in the User Provisioning request.
- Check the User's App User Profile to confirm that the Address Type attribute has a value as expected on the JumpCloud side.
- Then, attempt the user provisioning again. Go to the Okta admin Console and navigate to Dashboard > Tasks. Any failed assignments should appear under Tasks.
- After identifying the failed task for the user that should be retried, click on Retry Selected.
- If the issue persists, please contact JumpCloud support for more details and steps on how to resolve this error.
