This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(12.8, 44%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMA%3C/text%3E%3C/svg%3E)
Hi folks,
I am trying to provision a user from Microsoft Azure AD to a SaaS application I created as an enterprise application. Basically I want to be able to do CRUD operations on any user. Initially I have tried creating the user and the creation was successful. However, I am getting an error when I try to update the user details in Azure AD and then provision the user for the SaaS app. The below is the error I am having on "Provision on Demand":
"status":400,"error":"Bad Request","message":"JSON parse error: Could not resolve type id 'Add' as a subtype of com.unboundid.scim2.common.messages.PatchOperation: known type ids = [add, remove, replace] (for POJO property 'Operations'); nested exception is com.fasterxml.jackson.databind.exc.InvalidTypeIdException: Could not resolve type id 'Add' as a subtype of com.unboundid.scim2.common.messages.PatchOperation: known type ids = [add, remove, replace] (for POJO property 'Operations')\n at [Source: (PushbackInputStream); line: 1, column: 82] (through reference chain: com.unboundid.scim2.common.messages.PatchRequest["Operations"]->java.util.ArrayList[0])","path":"/scim/v2/5e4231ad-e4ac-2213-0c59-3a4e3139858c/Users/3e7600bb-7f90-e234-1512-122f78784fe8"}
The error you're seeing is being returned by the application in the HTTP response it sends back to Azure AD/Entra ID. You (or the developer, if that isn't you) will need to debug it.
Hi Danny, Thanks for your reply! I understand the error is being returned from the application. However, I believe its due to the request from Azure AD. The patch request from Azure AD contains an Operation ("Op") with upper leading char which is causing the issue at the application side since its expecting one of three values for op all in lower case ('add', 'remove', 'replace').