Miro provisioning flow fails with the following error visible in the Okta dashboard:

Automatic provisioning of user <username> to app Miro failed: Error while verifying if user <username> exists: 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')

• Miro
• Provisioning
• Error
• System for Cross-domain Identity Management (SCIM)

The permissions for the account used to enable SCIM provisioning are incorrect on the Miro side, or the API Credentials (Base URL or API Token) used to create the API connection are invalid.

1. On Miro's side, verify that the permissions for the account used to enable SCIM provisioning are correct.

2. Go to Okta Admin Console and navigate to Applications > Applications > Miro > Provisioning > Integration > Edit.

3. In Base URL, enter the Base URL from Miro.

4. In the API Token field, enter the Miro API token.

5. Click Test API Credentials, verify the connection was successful, and then click Save.

6. Attempt the failed tasks again. Navigate to Dashboard > Tasks. Any failed assignments should appear under Tasks.

7. After identifying the failed task for the user that should be retried, click on Retry Selected.