RFC 7644, "System for Cross-domain Identity Management: Protocol", September 2015

Errata ID: 7916
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Francois LASNE
Date Reported: 2024-04-29
Verifier Name: Deb Cooley
Date Verified: 2024-05-11

Section 3.7.3 says:

 containing a human-readable explanation of the error.

   "status": "201"

   The following is an example of a status in a failed operation.

  "status": "400",
  "response":{
       "schemas": ["urn:ietf:params:scim:api:messages:2.0:Error"],
       "scimType":"invalidSyntax"
       "detail":
  "Request is unparsable, syntactically incorrect, or violates schema.",
       "status":"400"
   }

It should say:

 containing a human-readable explanation of the error.

 The following is an example of a status in a failed operation.

  {
     "status": "400",
     "schemas": ["urn:ietf:params:scim:api:messages:2.0:Error"],
     "scimType":"invalidSyntax",
     "detail":"Request is unparsable, syntactically incorrect, or violates schema.",
   }

Notes:

it misses a { at the beginning of the 400 sample
it missies a , after invalidSyntax

the overall response looks wrong

Notice that even putting a there can be questionnable as well , and an alternative would be to just drop the content mentionned

SecAD Summary of the changes (per the authors):
* Remove line: “status”: “201”
* Add leading brace ‘{‘
* Add missing comma after “invalidSyntax”

Report New Errata