We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
null
If I post a SCIM POST request to the server with a null value for emails, I receive:
emails
{ "schemas": [ "urn:ietf:params:scim:api:messages:2.0:Error" ], "status": "400", "scimType": "invalidValue", "detail": "attribute emails is not an array" }
Similarly, if I POST a request with a null value for a schema attribute, I get an error as well:
{ "schemas": ["urn:ietf:params:scim:schemas:core:2.0:User","urn:ietf:params:scim:schemas:extension:enterprise:2.0:User"], "externalId": "external", "userName": "{{$guid}}", "emails": null, "urn:ietf:params:scim:schemas:extension:enterprise:2.0:User": null, "name": { "formatted": "formatted", "givenName": "givenName", "middleName": "middleName", "familyName": "familyName" } }
{ "schemas": [ "urn:ietf:params:scim:api:messages:2.0:Error" ], "status": "400", "scimType": "invalidValue", "detail": "Property urn:ietf:params:scim:schemas:extension:enterprise:2.0:User cannot contains an array" }
I can do some extra work serializing to omit nulls, but maybe this should be handled more gracefully by the server?
The text was updated successfully, but these errors were encountered:
Ticket #823 : Can pass null value
6aa7c93
The issue is fixed in the branch Release503 :
Release503
Sorry, something went wrong.
simpleidserver
No branches or pull requests
If I post a SCIM POST request to the server with a
null
value foremails
, I receive:Similarly, if I POST a request with a
null
value for a schema attribute, I get an error as well:I can do some extra work serializing to omit nulls, but maybe this should be handled more gracefully by the server?
The text was updated successfully, but these errors were encountered: