Invalid Schemas 400 Error When Trying To Update A User Using Fusion Apps REST API Through OIC REST Adapter
(Doc ID 2745476.1)
Last updated on JANUARY 21, 2021
Applies to:
Oracle Integration-OIC - Version 18.2.5 and laterInformation in this document applies to any platform.
Symptoms
REST PATCH method - /hcmRestApi/scim/Users/{id} to update a User using REST Adapter fails with following error
ERROR
-----------------------
<nstrgdfl:APIInvocationError
xmlns:nstrgdfl="http://xmlns.oracle.com/cloud/generic/rest/fault/REST/InvokeUserToNewUserCategory"><nstrgdfl:type/><nstrgdfl:title/><nstrgdfl:detail/><nstrg
dfl:errorCode/><nstrgdfl:errorDetails><nstrgdfl:type>http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.1</nstrgdfl:type><nstrgdfl:title>Bad
Request</nstrgdfl:title><nstrgdfl:errorCode>400</nstrgdfl:errorCode><nstrgdfl:
errorPath><![CDATA[PATCH
xmlns:nstrgdfl="http://xmlns.oracle.com/cloud/generic/rest/fault/REST/InvokeUserToNewUserCategory"><nstrgdfl:type/><nstrgdfl:title/><nstrgdfl:detail/><nstrg
dfl:errorCode/><nstrgdfl:errorDetails><nstrgdfl:type>http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.1</nstrgdfl:type><nstrgdfl:title>Bad
Request</nstrgdfl:title><nstrgdfl:errorCode>400</nstrgdfl:errorCode><nstrgdfl:
errorPath><![CDATA[PATCH
https://xxxxxxxxxxxxxxx.oraclecloud.com/hcmRestApi/scim/Users/xxxxxxxxxxxxnnnnn returned a response status of 400 Bad
Request]]></nstrgdfl:errorPath><nstrgdfl:instance><![CDATA[{
"Errors" : [ {
"description" : "Invalid schemas,expected value should contain
urn:scim:schemas:core:2.0:User",
"code" : "400"
} ]
}.A 400 Bad Request Error indicates that the target service is unable (or
refuses) to process the request sent by the client (Oracle Integration
Cloud), due to an issue that is perceived by the server to be a client
problem. You can trace the cURL representation of the request sent to the
target service from the Oracle Integration Cloud server logs. Try invoking
the target service using cURL. It may also be that one of the intermediaries
(proxy, LBR) could be returning this code.
]]><
"Errors" : [ {
"description" : "Invalid schemas,expected value should contain
urn:scim:schemas:core:2.0:User",
"code" : "400"
} ]
}.A 400 Bad Request Error indicates that the target service is unable (or
refuses) to process the request sent by the client (Oracle Integration
Cloud), due to an issue that is perceived by the server to be a client
problem. You can trace the cURL representation of the request sent to the
target service from the Oracle Integration Cloud server logs. Try invoking
the target service using cURL. It may also be that one of the intermediaries
(proxy, LBR) could be returning this code.
]]><
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |