---
title: Troubleshooting the SCIM 2.0 servlet extension
description: To troubleshoot the System for Cross-domain Identity Management (SCIM) 2.0 servlet extension, you must enable the Debug Trace Logger.
component: pingdirectory
version: 11.1
page_id: pingdirectory:managing_scim:pd_proxy_troubleshoot_scim_2_servelet_ext
canonical_url: https://docs.pingidentity.com/pingdirectory/11.1/managing_scim/pd_proxy_troubleshoot_scim_2_servelet_ext.html
llms_txt: https://docs.pingidentity.com/pingdirectory/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
revdate: 2026-08-17T00:00:00Z
page_aliases: ["managing_scim_11_and_20_servlet_extensions:pd_proxy_troubleshoot_scim_2_servelet_ext.adoc"]
section_ids:
  steps: Steps
  example: Example:
  result: Result:
---

# Troubleshooting the SCIM 2.0 servlet extension

To troubleshoot the System for Cross-domain Identity Management (SCIM) *(tooltip: \<div class="paragraph">
\<p>An application-level, HTTP-based protocol for provisioning and managing user identity information. SCIM supplies a common schema for representing users and groups and provides a REST API.\</p>
\</div>)* 2.0 servlet extension, you must enable the Debug Trace Logger.

For security reasons, error messages specifically regarding LDAP systems are suppressed and don't appear in the HTTP responses from the server. Instead, the response displays something like the following.

```json
{
	"schemas": [
	"urn:ietf:params:scim:api:messages:2.0:Error"
	],
	"status": "400",
	"detail": "Request failed: correlationID='073eb1a8-8c51-48b3-83a0-380e1d4b4ab9'"
}
```

## Steps

* To access these messages, enable the Debug Trace Logger through the admin console or with the following `dsconfig` command.

  ### Example:

  ```
  dsconfig set-log-publisher-prop --publisher-name "Debug Trace Logger" \
  			--set enabled:true --add scim-message-type:error
  ```

  ### Result:

  After you enable the Debug Trace Logger, the server begins logging information related to SCIM operations to the `/logs/debug-trace` file, as in the following example.

  ```
  [09/Jun/2020:05:23:10.992 -0500] HTTP REQUEST requestID=3
  correlationID="073eb1a8-8c51-48b3-83a0-380e1d4b4ab9" product="Ping Identity
  Directory Server" instanceName="example" startupID="Xt9fJg==" threadID=173
  from=[0:0:0:0:0:0:0:1]:53978 method=POST
  url="https://0:0:0:0:0:0:0:1:9443/scim/v2/Users"
  ```

  |   |                                                                                                                                                                                                           |
  | - | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
  |   | The presence of `correlationID` in these messages allows for matching the ID in the HTTP responses to the messages in the `debug-trace` log so that the appropriate LDAP error message can be determined. |