Overview#

Reference typically is a data-type and implies a reference as in by-reference.

SCIM 2.0#

Reference is a URI for a Resource. S resource MAY be a SCIM resource, an external link to a resource (e.g., a photo), or an identifier such as a URN.

The value MUST be the absolute or relative URI of the target resource. Relative URIs should be resolved as specified in Section 5.2 of RFC 3986. However, the base URI for relative URI resolution MUST include all URI components and path segments up to, but not including, the Endpoint URI (the SCIM Service Provider root endpoint); e.g., the base URI for a request to "https://example.com/v2/Users/2819c223-7f76-453a-919d-413861904646" would be https://example.com/v2/", and the relative URI for this resource would be "Users/2819c223-7f76-453a-919d-413861904646".

In JSON representation, the URI value is represented as a JSON string per Section 7 of RFC 7159. A reference is case exact. A reference has a "referenceTypes" attribute that indicates what types of resources may be linked, as per Section 7 of this document.

A reference URI MUST be to an HTTP-addressable resource. An HTTP client performing a HTTP GET operation on a reference URI MUST receive the target resource or an appropriate HTTP response code. A SCIM service provider MAY choose to enforce referential integrity for reference types referring to SCIM Resources.

By convention, a reference is commonly represented as a "$ref" sub-attribute in complex or multi-valued attributes; however, this is OPTIONAL.

LDAP Attribute Definition#

The Reference AttributeTypes is defined as:

More Information#

There might be more information for this subject on one of the following:

Add new attachment

Only authorized users are allowed to upload new attachments.
« This page (revision-6) was last changed on 30-Jul-2016 20:50 by jim