SAP Provisioning flow fails with the following error:
Error authenticating: message=Invalid JSON received from the SCIM server. Cannot parse the JSON. error=Unexpected character ('<' (code 60)): expected a valid value (JSON String, Number, Array, Object or token 'null', 'true' or 'false') at [Source: <Source> (`StreamReadFeature.INCLUDE_SOURCE_IN_LOCATION` disabled); line: 27, column: 1]
The connector configuration could not be tested. Make sure that the URL, Authentication Parameters are correct and that there is an implementation available at the URL provided.
- System for Cross-domain Identity Management (SCIM) 2.0 Integrations
- Provisioning
- Okta Classic Engine
- Okta Identity Engine (OIE)
This error indicates that Okta is receiving an HTML response (often an error page) instead of a valid JSON payload from the App SCIM endpoint.
This usually happens when:
- The SCIM endpoint URL is incorrect or points to an invalid SCIM-compliant endpoint.
- The authentication credentials (API token, bearer token, or secret key) are invalid or missing.
- The SCIM server is returning an HTML status code (for example, 404 or 500) instead of a JSON response.
- The SCIM server is down, in maintenance mode, or blocked by a firewall.
To resolve this, please verify the following:
- Verify that the SCIM base URL and protocol (HTTPS) are correct.
- Confirm that the App SCIM endpoint returns valid JSON by testing it directly with a tool like Postman or curl using the same credentials (for example,
GET /Users). - Ensure the SCIM server is online and accessible from Okta’s IP ranges.
- Check the App server logs to confirm whether the request from Okta is received and if any internal errors are logged.
- Once the endpoint returns valid JSON, retry the connector configuration test in Okta.
