SCIM 2.0 Token Search Extension
draft-hunt-scim-tokensearch-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Phil Hunt , Kelly Grizzle , Morteza Ansari , Dale Olds | ||
| Last updated | 2013-06-26 (Latest revision 2012-12-23) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The SCIM 2.0 Core API defines a simple profile for searching for specific resource types using filters and qualifiers in combination with the HTTP GET verb. The Token Search specification defines the following additional features: o Specification of search terms within an HTTP POST verb to avoid accidental leakage of confidential information via HTTP GET URLs, o An optional result set token enabling clients to page through results in a state consistent fashion, and o The ability to search across multiple resource types (endpoints) and return one or more resource types.
Authors
Phil Hunt
Kelly Grizzle
Morteza Ansari
Dale Olds
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)