Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

violation of RFC7643 "Unassigned and Null Values" #120

Closed
Captain-P-Goldfish opened this issue Jul 22, 2018 · 0 comments · Fixed by #123
Closed

violation of RFC7643 "Unassigned and Null Values" #120

Captain-P-Goldfish opened this issue Jul 22, 2018 · 0 comments · Fixed by #123

Comments

@Captain-P-Goldfish
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant