---
sourceDocument: Australia Platform security
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/platform-security

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# SCIM Client troubleshooting

# SCIM Client troubleshooting {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of SCIM Client Troubleshooting

This guide provides troubleshooting actions to resolve common issues encountered when setting up or using the SCIM Client in ServiceNow.
Understanding these troubleshooting steps can help ensure successful API calls and proper configuration.
Show full answer Show less  

## Key Features

* **Error Messages:** Identify issues based on specific error messages returned by the API. For example, messages may indicate access control issues, authentication failures, or incorrect data types.
* **SCIM Client Logs:** Utilize logs to trace API calls, identify the status of requests, and review error messages related to SCIM operations.
* **Request Body Configuration:** Ensure proper configuration and validation of request bodies to avoid issues related to payload data.

## Key Outcomes

By following the troubleshooting actions outlined, customers can expect to:

* Resolve access control issues by ensuring the API is called in the system context.
* Authenticate successfully by verifying that the token is valid and generated correctly.
* Ensure data integrity by passing valid IDs expected by SCIM attributes.
* Enhance logging capabilities to capture detailed information for better diagnostics.  
Troubleshooting actions can help resolve common issues when setting up or running the
SCIM Client.
{#scim-client-troubleshooting__table_mxt_czm_htb__entry__2}

| Issue | Action |
|-|-|
| Response contains the following message: "message":"Unable to access the table core_company with id: 0c441abbc6112275000025157c651c89, Please cross check the Access control rules" | The message is displayed if the API is called in a user context and the user does not have access to the table. You must make sure that the scriptable API is called in the system context. |
| Response contains the following message: {"message":"User Not Authenticated","detail":" Required to provide Auth information"} | * Make sure that the token is generated through the corresponding REST message and it is valid. * Make sure that the scriptable API is called in the system context. {#scim-client-troubleshooting__ul_rhd_yvh_3tb} |
| Response contains the following message: Script execution failed, the reason is: Cannot cast java.lang.Integer to java.lang.String | In the SCIM attribute mapping, if the field is defined to fetch from a script with this issue, then make sure that the return type should always be a string. |
| Response contains the following message: "status": "400", "scimType": "invalidValue", "detail": "Manager id : 02826bf03710200044e0bfc8bcbe5ds8 doesn't exist" | For any SCIM attribute that expects the ID, then that ID is always of the provider system. Make sure the ID that is passed in the payload is valid in the provider system. |
[Table 1. Troubleshooting]

{#scim-client-troubleshooting__table_mxt_czm_htb}

## Areas to check for troubleshooting {#scim-client-troubleshooting__section_vgr_4wh_3tb}

The following are some of the areas that can be checked for troubleshooting errors when
using the SCIM Client:

* If any issue is found while running any of the scriptable APIs, see the SCIM Client logs section. {#scim-client-troubleshooting__table_kcs_wwh_3tb__entry__2}

  | Field | Description |
  |-|-|
  | Request ID | Unique ID that represents a scriptable API called. |
  | SCIM Provider | Provider name for which the API is called. |
  | Resource | Name of the resource for which the API is called. |
  | Resource ID | The ID for which the API is called. For deletion, the ID represents the resource ID in the provider system and the ID is in the client system. |
  | Action | API that is called |
  | Status | Status of the log as a success or failure |
  | Message | Success or error message. The error message can be from the SCIM provider or because of configuration issues in the SCIM Client. |
  [Table 2. Logs Fields]

  {#scim-client-troubleshooting__table_kcs_wwh_3tb}
* Check the request body by configuring and viewing outbound calls. To learn more, see [Outbound web services
  logging](https://www.servicenow.com/docs/access?context=outbound-request-logging&version=australia&pubname=australia-api-reference&ft:locale=en-US).
* Update log levels by adding the content-type, testing the sample, and navigating to corresponding the HTTP Method form in the REST message of the corresponding provider.
* If the request body is truncated, then increase the limit by using system property glide.outbound_http.content.max_limit.
{#scim-client-troubleshooting__ul_dbg_swh_3tb}