Please find the detailed information regarding our SCIM implementation:
- Add Operations
In our SCIM implementation, the 'add' operation is supported using the following request body format, where the attribute is included directly within the value object — without specifying a path:
{
"schemas": [
"urn:ietf:params:scim:api:messages:2.0:PatchOp"
],
"Operations": [
{
"op": "add",
"value": {
"urn:ietf:params:scim:schemas:extension:signalsnotebook:2.0:UserProperties": {
"alias": "xyz"
}
}
}
]
}
This format is necessary for the 'add' operation due to the way our system processes the custom SCIM extension schema for UserProperties
2. 'Replace' Operation:
Alternatively, you can use the 'replace' operation with a fully qualified path. The request body for this operation is as follows:
{
"schemas": [
"urn:ietf:params:scim:api:messages:2.0:PatchOp"
],
"Operations": [
{
"op": "replace",
"path": "urn:ietf:params:scim:schemas:extension:signalsnotebook:2.0:UserProperties:alias",
"value": "abc"
}
]
}
Comments
0 comments
Article is closed for comments.