This document compares the CIFER API against SCIM v2 for suitability in a complex University Profile scenario.

Portions in red indicate changes need in the CIFER API or extension required for SCIM.

Retrieve

CIFER Read API

GET /v1/people/network/jqs23



HTTP/1.1 200 OK

Content-Type: application/json

ETag: W/"a330bc54f0671c9"



{

  "meta":{

    "resource":{

      "release":"public",

    },

    "lastModified":"2014-06-16T03:05:17Z"

  }

}

SCIM 2.0

GET /v2/Users/network:jqs23



HTTP/1.1 200 OK

Content-Type: application/json

Location: https://example.edu/v2/Users/network:jqs23

ETag: W/"a330bc54f0671c9"



{

}

Open Questions

  1. For both, what is the canonical location if a user resource can be accessed via multiple identifier types?

Update

  • No labels