Opened 9 years ago

Closed 9 years ago

#42 closed defect (fixed)

Consider making server root searches optional

Reported by: kelly.grizzle@… Owned by: phil.hunt@…
Priority: major Milestone:
Component: api Version:
Severity: - Keywords:
Cc:

Description

In issue #25, the ability to search against the server root was added:

Queries MAY be performed against a SCIM:

Resource (e.g. /Users/{userid}),
Resource Type endpoint (e.g. /Users or /Groups), or
Server Root (e.g. /).

However, for some service providers it may be difficult to perform a server root query that performs well at scale.

See the discussion on the mailing list here: http://www.ietf.org/mail-archive/web/scim/current/msg01027.html

Change History (4)

comment:1 Changed 9 years ago by phil.hunt@…

  • Owner changed from draft-ietf-scim-api@… to phil.hunt@…

comment:2 Changed 9 years ago by phil.hunt@…

Proposed text. Replace section 3.2.2.1 Query Endpoints with:

3.2.2.1 Query Enpoints

Resource Queries

A query MAY be performed against any specific resource endpoint or resource. For example:

  • Resource (e.g. /Users/{userid}),
  • Resource Type endpoint (e.g. /Users or /Groups)

Root Queries

A server MAY support queries at the server root (e.g. /) for the purpose of returning resources of more than one resource type.

A search against a server root indicates that ALL resources within the server SHALL be included subject to filtering. For example, a filter against 'meta.resourceType' could be used to restrict results to one or more specific resource types.

When processing search operations across endpoints that include more than one SCIM resource type (e.g. a search from the server root endpoint), filters MUST be processed in the same fashion as outlined in Section 3.2.2.2. For filtered attributes that are not part of a particular resource type, the service provider SHALL treat the attribute as if there is no attribute value. For example, a presence or equality filter for an undefined attribute evaluates as FALSE.

comment:3 Changed 9 years ago by kelly.grizzle@…

I like the text. However, I think the ServiceProviderConfig? should specify whether root search is supported or not. Proposed text:

Schema doc section 9 (Service Provider Configuration Schema) – add the following attribute between the filter and changePassword attributes:

rootSearch A complex type that specifies root search configuration options. REQUIRED.

supported Boolean value specifying whether root search is supported. REQUIRED.

comment:4 Changed 9 years ago by phil.hunt@…

  • Resolution set to fixed
  • Status changed from new to closed

Implemented in draft 03

Note: See TracTickets for help on using tickets.