Every time a CMiC connector runs, it has to authenticate first, either with a CMiC user name and password, or with an OAuth application (a Client ID, Secret, and Scope registered with your identity provider). If those credentials are wrong or expired, or if the CMiC Service URL on the connector is mistyped, CMiC or the identity provider rejects the connection before any employee data can move.
Where you see the failure depends on when it happens. Testing the connector on its configuration page produces one of the OAuth-specific messages below, translated from a code the identity provider returned. The same kind of failure happening during an actual sync run instead produces one of two short, generic messages, translated from the raw CMiC API response text.
Error Messages
These are connection-level failures, not record-level data errors, so the Direction column below names the surface where the message appears instead of a read/write direction: Test Connection (the connector's Test Connection check, no sync data moves either way) or Sync run (a live scheduled or manual sync execution).
| Message text | Direction | Occurs when | Outcome | Fix |
|---|---|---|---|---|
| CMiC Provider failed to authenticate. Please review the UserName and password and try it again. | Sync run | The live CMiC API response contains the exact, case-sensitive text "The request requires user authentication" (a 401-style rejection). | Almost always fires during connector setup, before this entity's records are read or written: the whole entity is skipped and logged as a step-level Failure, not as an Error on that entity. Rarely, if credentials stop working partway through a run, only the one record being written at that moment is skipped and the run continues. | Re-enter and save the CMiC UserName and Password on the connector, then test the connection again. |
| Name or Service URL not known | Sync run | The live CMiC API response contains the exact, case-sensitive text "The server has not found anything matching the Request-URI" (a 404-style response). | Same pattern as the credentials message above: almost always a step-level Failure with the whole entity skipped (zero records processed), because the bad URL fails the very first call the connector makes. | Verify and correct the CMiC Service URL on the connector configuration, then test the connection again. |
| The client secret has expired. Please update the OAuth Secret in the connector configuration with a new client secret. | Test Connection | Testing an OAuth-configured connector; the identity provider's rejection contains the code AADSTS7000222. | The connection test returns unsuccessful with this message. No sync data moves. | You (or your administrator) issue a new client secret for the application and enter it in the connector's OAuth Secret field. |
| Invalid client credentials. Please verify the OAuth Client ID and OAuth Secret are correct in the connector configuration. | Test Connection | The identity provider's rejection contains the code AADSTS7000215, or the literal text "invalid_client". | The connection test returns unsuccessful with this message. No sync data moves. | Re-check the OAuth Client ID and OAuth Secret on the connector against the values registered with your identity provider. |
| The application was not found in the directory. Please verify the OAuth Client ID is correct and the application is registered in your identity provider. | Test Connection | The identity provider's rejection contains the code AADSTS700016. | The connection test returns unsuccessful with this message. No sync data moves. | Verify the OAuth Client ID matches an application that is actually registered in your identity provider directory. |
| The client is not authorized to use this authentication method. Please contact your administrator to verify the application permissions. | Test Connection | The identity provider's rejection contains the code AADSTS650053. | The connection test returns unsuccessful with this message. No sync data moves. | Contact your administrator (see Open questions) to grant the application permission to use this authentication method. |
| The requested OAuth Scope is invalid or not authorized. Please verify the OAuth Scope in the connector configuration. | Test Connection | The identity provider's rejection contains the code AADSTS70011, or the literal text "invalid_scope". | The connection test returns unsuccessful with this message. No sync data moves. | Verify and correct the OAuth Scope value on the connector configuration. |
| Access was denied by the identity provider. Please verify the application has the necessary permissions and consents. | Test Connection | The identity provider's rejection contains the code AADSTS65001, or the literal text "access_denied". | The connection test returns unsuccessful with this message. No sync data moves. | You (or your administrator) grant the application the permissions and consents it is asking for in your identity provider. |
| The Provider could not connect and verify the provided configuration. Check the values and Test the connection again. | Test Connection | Test Connection failed, but neither the exception nor any inner exception in its chain contained any of the six codes or phrases above. This is the catch-all fallback, and it is also what a plain CMiC user name/password (non-OAuth) authentication failure looks like on this screen, since that path never produces an AADSTS-style code. | The connection test returns unsuccessful with this message. No sync data moves. | Re-check every connector configuration value (Service URL, and either UserName/Password or OAuth Client ID/Secret/Scope), then test again. |
Confirming the Error
- To see a Test Connection result: open the connector's configuration and run Test Connection (or Test). Compare the returned message text word-for-word against the Message text column above.
- To find a sync-run message: open the sync execution in Sync History, then open the step for this CMiC connector.
- The Sync History screen shows per-entity counts labelled Errors, Warnings, Information, Failures, Added, Updated, and Unchanged. For this family, check the step's Failures count first, not any one entity's Errors count.
- For ProviderErrorCredentials and Name or Service URL not known, the usual signature is a step-level Failures entry containing the message text, while the affected entity's own row shows Total, Added, Updated, Unchanged, and Errors all at zero. That zeroed-out row is expected here, it is not a separate bug: the entity never got past connector setup, so it never processed any records.
- If instead you find the message inside one specific entity's Errors list, only that one record failed (credentials stopped working partway through the run); the rest of that entity's records will still show normal Added, Updated, or Unchanged counts.
- Match on the fixed part of the sentence in every case. None of the messages in this family contain variable data, so an exact text match is expected every time.
Resolving the Error
Cmic Provider Failed to Authenticate/Name or Service URL Not Known
- Open the connector's configuration for this CMiC connector.
- For the authentication message, re-enter and save the CMiC UserName and CMiC Password fields.
- For the URL message, verify the CMiC Service URL exactly matches the CMiC environment address.
- Save the connector, run Test Connection, and confirm it returns success before re-running the sync.
Oauth Test Connection Messages (Client Secret, Client Credentials, Application Not Found, Unauthorized Client, Scope, Access Denied)
- Open the connector's configuration for this OAuth-configured CMiC connector.
- For an expired or invalid client secret, or invalid client credentials, obtain a new OAuth Secret (and confirm the OAuth Client ID) from your identity provider and re-save both fields.
- For application not found, confirm the OAuth Client ID matches an application actually registered with your identity provider.
- For invalid scope, verify and correct the OAuth Scope value on the connector.
- For unauthorized client or access denied, these point to application permissions and consent that only your administrator can grant; have your administrator review and approve the application's permissions.
- Save the connector, run Test Connection, and confirm it returns success.
The Provider Could Not Connect and Verify the Provided Configuration
- Re-check every value on the connector configuration: CMiC Service URL, and either CMiC UserName/Password or OAuth Client ID/Secret/Scope.
- Correct any values that look wrong, save, and run Test Connection again.
- If it still fails after all values look correct, escalate; this message does not tell you what actually went wrong.
When to Escalate
If any of the following occur, you may need to reach out to Arcoro support for additional assistance.
- The Provider could not connect and verify the provided configuration message persists after every configuration value has been re-checked and re-saved. Escalate with the ticket, since this message intentionally hides the underlying cause.
- The client is not authorized to use this authentication method or Access was denied by the identity provider keeps appearing after your administrator has already granted permissions. Escalate rather than repeating the same instruction.
- CMiC Provider failed to authenticate or Name or Service URL not known appears on a connector that tested successfully on a previous run, with no configuration change on the Arcoro side. Escalate, since your CMiC environment or credentials likely changed outside Arcoro.
- You believe your values are correct and the same message keeps recurring.