Re: [scim] Proposed resolution - root search optionality (ticket 42)

[Kelly Grizzle <[e-mail]>]

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.

--Kelly

From: [e-mail] [mailto:[e-mail]] On Behalf Of Leif Johansson
Sent: Tuesday, October 29, 2013 3:23 PM
To: [e-mail]
Subject: Re: [scim] Proposed resolution - root search optionality (ticket 42)

On 10/29/2013 07:28 PM, Kelly Grizzle wrote:
I like the text, but think that we should also consider adding a ServiceProviderConfig property that says whether this is supported or not.
Propose text ?


--Kelly

From: [e-mail]<mailto:[e-mail]> [mailto:[e-mail]] On Behalf Of Anthony Nadalin
Sent: Monday, October 28, 2013 3:48 PM
To: Phil Hunt; [e-mail]<mailto:[e-mail]> WG
Subject: Re: [scim] Proposed resolution - root search optionality (ticket 42)

+1

From: [e-mail]<mailto:[e-mail]> [mailto:[e-mail]] On Behalf Of Phil Hunt
Sent: Monday, October 28, 2013 11:47 AM
To: [e-mail]<mailto:[e-mail]> WG
Subject: [scim] Proposed resolution - root search optionality (ticket 42)


Proposed text. Replace section 3.2.2.1 Query Endpoints with (ticket 42 - http://trac.tools.ietf.org/wg/scim/trac/ticket/42 ):

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.
Please confirm if you agree with this subtle change which makes root searches optional to the server.

Phil

@independentid
www.independentid.com<http://www.independentid.com>
[e-mail]<mailto:[e-mail]>





_______________________________________________

scim mailing list

[e-mail]<mailto:[e-mail]>

https://www.ietf.org/mailman/listinfo/scim