Working Drafts
This page collects our draft specifications and other auxiliary material, and various other useful materials that may contribute to them. See the list of child pages at the bottom for a summary.
The following diagram illustrates the "call tree" of key specifications and other documents that are relevant to the UMA work. Click on boxes in the diagram to get the corresponding document.
<map name="GraffleExport">
<area shape=poly coords="240,132,257,103,291,103,319,125,302,154,268,154,240,132" href="http://kantarainitiative.org/confluence/display/uma/User+Stories">
<area shape=rect coords="95,487,169,537" href="http://tools.ietf.org/html/rfc5785">
<area shape=rect coords="28,487,87,537" href="http://docs.oasis-open.org/xri/xrd/v1.0/xrd-1.0.html">
<area shape=rect coords="47,404,147,454" href="http://tools.ietf.org/html/draft-hammer-hostmeta-13">
<area shape=rect coords="374,47,489,114" href="http://kantarainitiative.org/confluence/display/uma/Simple+Access+Authorization+Claims">
<area shape=poly coords="514,176,531,147,565,147,593,169,576,198,542,198,514,176" href="http://kantarainitiative.org/confluence/display/uma/User+Experience#UserExperience-UMATrustedClaims">
<area shape=poly coords="240,210,257,180,291,180,319,202,302,231,268,231,240,210" href="http://kantarainitiative.org/confluence/display/uma/UMA+Scenarios+and+Use+Cases">
<area shape=poly coords="535,262,552,233,586,233,614,255,597,284,563,284,535,262" href="http://kantarainitiative.org/confluence/display/uma/UMA+Trust+Model">
<area shape=poly coords="240,287,257,258,291,258,319,280,302,309,268,309,240,287" href="http://kantarainitiative.org/confluence/display/uma/UMA+Requirements">
<area shape=rect coords="374,146,489,196" href="http://kantarainitiative.org/confluence/display/uma/Claims+2.0">
<area shape=rect coords="490,326,650,376" href="http://tools.ietf.org/html/draft-hardjono-oauth-dynreg-00">
<area shape=rect coords="352,442,511,492" href="http://tools.ietf.org/html/draft-ietf-oauth-v2">
<area shape=rect coords="352,229,511,279" href="http://kantarainitiative.org/confluence/display/uma/UMA+1.0+Core+Protocol">
</map>
<img border=0 src="http://kantarainitiative.org/confluence/download/attachments/17301540/spec-modules.png" usemap="#GraffleExport">
Specifications in Progress
We are currently using Eve's UMA-Specifications area on github – https://github.com/xmlgrrl/UMA-Specifications – for our active spec development, with snapshots provided on this wiki. Following is an accounting of specs and their status.
Spec |
Description |
Status |
|---|---|---|
UMA Scenarios and Use Cases |
Records the scenarios and use cases governing the development of the User-Managed Access protocol and guiding associated implementations and deployments. |
Currently maintained directly on this wiki. Latest version is here. |
UMA User Stories |
Records the use cases in a clipped "user story" form similar to that used by the Agile methodology. |
Currently maintained directly on this wiki. Latest version is here. |
UMA Requirements |
Records the specific requirements governing the development of the User-Managed Access protocol and guiding associated implementations and deployments. |
Currently maintained directly on this wiki. Latest version is here. We treat design principles (beyond the ones in our charter) as "emergent", and collect them as we see fit. |
UMA 1.0 Core Protocol |
Defines the User-Managed Access (UMA) 1.0 core protocol. This protocol provides a method for users to control access to their protected resources, residing on any number of host sites, through an authorization manager that makes access decisions based on user policy. |
Latest version is here. The formatting doesn't look perfect due to Confluence wiki limitations. |
Resource registration |
Obsolete. Used to define the mechanism for hosts to convey important information about resources that the AM needs to protect. |
Now included directly in the core spec. |
Dynamic client registration |
Defines how hosts can dynamically discover information about an AM and how hosts and requesters can dynamically register at an AM to get a unique client identifier and optional secret. |
Some UMA group participants have contributed an Internet-Draft to the IETF on this, and hope to continue working on it as an OAuth WG action item. |
Claims 2.0 |
Defines a JSON-based format for expressing claims and requests for claims. |
Currently maintained directly on this wiki. Latest version is here. (See also the proposal for third-party-asserted "trusted claims".) |
Simple Access Authorization Claims |
Uses the Claims 2.0 specification to define a small set of basic claims to be used in the process of User-Managed Access (UMA) access authorization. |
Currently maintained directly on this wiki. Latest version is here. |
UMA Trust Model |
Explores operational, contractual, and legal issues raised by the act of using User-Managed Access (UMA) to authorize another party to get web resource access. |
Currently maintained directly on this wiki. Latest version is here. |