Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

UMA Explained

User-Managed Access (UMA) involves these entities:

...

See the following sections for suggested reading. Be sure to read the documents in the Working Drafts area of this wiki for the official definition of UMA.

General Interest

  • Slides from a half-day workshop held at the European Identity Conference in Munich on 4 May 2010.
  • The User Experience page collects wireframes exploring user interactions with UMA-enabled services. This includes a set of wireframes that matches the webinar scenario.
  • We have a working lexicon that explores the relationship between the party who authorizes access and the party who ultimately gets access. Lawyerly types might be especially interested in this.
  • Group chair Eve Maler writes about UMA and its predecessor, ProtectServe, here.
  • Some historical materials (may be out of date) explaining the original thinking behind UMA and its predecessor, ProtectServe, are available.

Implementers and Deployers

Following is a condensed summary of the draft UMA protocol:

Image Removed

See also the following:

  • Christian Scholz has done a very simple prototype of the UMA protocol in Python.
  • These slides from IIW in May 2010 (and this blog post) explain how UMA compares to OAuth.
  • A comprehensive technical report published under the auspices of Newcastle University called User-Managed Access to Web Resources (also available on ncl.ac.uk site) explains the requirements that drive UMA, analyzes the design features that respond to these requirements, and reviews related work.
  • The Protocol Flow page has swimlane diagrams that show the core protocol at a high level.
  • The Technology Matrix compares UMA with various other technologies and explores potential synergies between them.

...

This is now a historical page. Historical materials are stored underneath this page.