SimpleIdServer icon indicating copy to clipboard operation
SimpleIdServer copied to clipboard

[SCIM] Errors response body not according to the RFC

Open ZahiC opened this issue 3 years ago • 2 comments

Hi, I tried to run OKTA Runscope tests against Simple ID SCIM server. Most of the tests pass.

It failed on 404 error. For getting non-existing resource (user), it expects:

{
  "status": "404",
  "schemas": ["urn:ietf:params:scim:api:messages:2.0:Error"],
  "detail": "resource X not found"
}

While Simple ID response is:

{
  "status": "404",
  "response": {
    "schemas": ["urn:ietf:params:scim:api:messages:2.0:Error"],
    "status": "404",
    "detail": "resource X not found"
  }
}

It seems that the RFC expect the error response to be on the root of the response json:

image

I think it's also relevant for other error responses in the SCIM server.

ZahiC avatar Mar 07 '22 09:03 ZahiC

Hello,

Indeed there is a small issue in our SCIM implementation :) Thank you very much for your feedback ! We are going to fix it ASAP.

Kind Regards,

SimpleIdServer

simpleidserver avatar Mar 07 '22 12:03 simpleidserver

The issue is fixed in the branch "release/2.0.5".

Kind Regards,

SimpleIdServer

simpleidserver avatar Mar 07 '22 13:03 simpleidserver