---
title: SCIM 2.0 PATCH operations
description: You can use a PATCH request to modify a System for Cross-domain Identity Management (SCIM) 2.0 resource that has one or more required SCIM 2.0 attributes.
component: pingdirectory
version: 11.1
page_id: pingdirectory:managing_scim:pd_proxy_scim_2_patch_ops
canonical_url: https://docs.pingidentity.com/pingdirectory/11.1/managing_scim/pd_proxy_scim_2_patch_ops.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-19T00:00:00Z
page_aliases: ["managing_scim_11_and_20_servlet_extensions:pd_proxy_scim_2_patch_ops.adoc"]
section_ids:
  example: Example
---

# SCIM 2.0 PATCH operations

You can use a PATCH request to modify a 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 resource that has one or more required SCIM 2.0 attributes.

The requester needs permissions to read the values of these required attributes and write permissions for the attributes being modified, even if the PATCH request doesn't alter the requirements.

## Example

You can modify an LDAP Mapping SCIM 2.0 resource type using the following schema definition, where `uid` and `cn` are mapped to their LDAP equivalents.

```json
{
	"schemas": ["urn:ietf:params:scim:schemas:core:2.0:Schema"],
	"id": "urn:test:schema:person",
	"attributes": [
	{
	"name": "uid",
	"type": "string",
	"multiValued": false,
	"required": true,
	"caseExact": false,
	"mutability": "readWrite",
	"returned": "default",
	"uniqueness": "none"
	},
	{
	"name": "cn",
	"type": "string",
	"multiValued": false,
	"required": false,
	"caseExact": false,
	"mutability": "readWrite",
	"returned": "default",
	"uniqueness": "none"
	}
		],
		...
			}
```

The following PATCH operation fails if the SCIM 2.0 service account doesn't have access to both `uid` and `cn`.

```json
{
	"schemas": ["urn:ietf:params:scim:api:messages:2.0:PatchOp"],
	"Operations":[{
	"op":"add",
	"path":"cn",
	"value": "new cn value"
	}]
		}
```