You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Accoding to RFC7643 chapter 2.5 null values in the json request are allowed. But sending them results in Http status code 400 for invalid json syntax
2.5 Unassigned and Null Values
Unassigned attributes, the null value, or an empty array (in the case
of a multi-valued attribute) SHALL be considered to be equivalent in
"state". Assigning an attribute with the value "null" or an empty
array (in the case of multi-valued attributes) has the effect of
making the attribute "unassigned". When a resource is expressed in
JSON format, unassigned attributes, although they are defined in
schema, MAY be omitted for compactness.
The text was updated successfully, but these errors were encountered:
Accoding to RFC7643 chapter 2.5 null values in the json request are allowed. But sending them results in Http status code 400 for invalid json syntax
2.5 Unassigned and Null Values
Unassigned attributes, the null value, or an empty array (in the case
of a multi-valued attribute) SHALL be considered to be equivalent in
"state". Assigning an attribute with the value "null" or an empty
array (in the case of multi-valued attributes) has the effect of
making the attribute "unassigned". When a resource is expressed in
JSON format, unassigned attributes, although they are defined in
schema, MAY be omitted for compactness.
The text was updated successfully, but these errors were encountered: