Okta Provisioning Occurs for Zoom With an Invalid JSON Unexpected Character Error

A Zoom provisioning failure occurs when Okta receives an HTML response instead of JSON from the System for Cross-domain Identity Management (SCIM) endpoint. Re-authenticating the API connection resolves this issue. Okta displays the following error message indicating an unexpected character in the JSON response:

FAILURE: Not Acceptable. Errors reported by remote server: Invalid JSON: Unexpected character ('<' (code 60)): expected a valid value (JSON String, Number, Array, Object or token 'null', 'true' or 'false') at [Source: REDACTED StreamReadFeature.INCLUDE_SOURCE_IN_LOCATION disabled); line: 1

• Okta Identity Engine (OIE)
• Okta Classic Engine
• Okta Integration Network (OIN)
• Provisioning
• Zoom

This error occurs when Okta receives an HTML response, such as a 404/500 page or firewall block, instead of JSON from the SCIM endpoint. An incorrect endpoint URL or invalid or expired authentication credentials typically cause this behavior.

How is the Zoom provisioning error resolved?

Resolve the Zoom provisioning error by verifying the Zoom account permissions, re-authenticating the API connection within the Okta Admin Console, and retrying the failed provisioning tasks.

1. Review the Okta User Management with Zoom documentation. Access the Zoom administrator dashboard to verify that the account used to create the API connection possesses the necessary permissions.
2. Open an incognito or private browsing window and sign in to the Okta tenant using an administrator account.
3. Navigate to Applications > Applications in the Okta Admin Console, and select the Zoom application.
4. Select the Provisioning tab, choose the Integration settings in the left menu, and select Edit.
5. Select Re-authenticate with Zoom.
6. Enter the correct API credentials in the authentication prompt.
   • NOTE: Zoom will display a message prompting the administrator to enable the application for all users, along with a link to another Zoom page to enable the option.
7. Return to the Provisioning page in Okta and refresh the browser window.
8. Select Re-authenticate with Zoom a second time to ensure the connection is established correctly.
9. Select Save once Okta displays a successful re-authentication message.
10. Navigate to Dashboard > Tasks in the Okta Admin Console to retry the failed tasks, or attempt the user provisioning process again to confirm the resolution.