This page collects case studies. Please use the following template for creating new case studies, and create them as pages underneath this page. Planned and requested case studies:
- Street Identity++ (Maciej/Eve)
- Self-contained app (Eve/Neil, for eGov open data?: writeup)
- CV sharing for university students (Thomas/Maciej) - draft case study
- Parent-group sharing (Thomas: writeup)
- Enterprise management of scope authorization (Mike: OxAuth issue, draft swimlane)
- Online personal loan (Domenico) - draft case study
- EU-compliant user data-sharing control (Luk/Sampo?)
- Patient-centric healthcare data sharing and consent management (Adrian Gropper)
These case studies are designed to address "business-level" scenarios. For additional detail on OAuth-specific use cases, see the draft-ietf-oauth-use-cases document.
Case Study: fill-in-name
Introduction
Brief intro text, describing applicable audiences, vertical industry sectors, etc.
Problem Scenario
Brief problem statement
Current Situation
Optional subsection documenting how the problem is solved today, ideally with protocol and/or process flows.
Problems
Analysis of problems with current situation
Gaps in Other Technologies
Optional subsection documenting where OAuth, OpenID Connect, SAML, etc. are insufficient or inappropriate.
Proposed Improvements
Brief statement of how UMA will be used as an improvement
Solution Scenario
Identify the UMA "constellation", likely policy statements needed, OAuth grant flows likely to be leveraged (how parties authenticate into the AM to get PATs and AATs issued), system rules/trust framework/binding obligations implications, etc.
Solution Flow
Detail how the UMA protocol and any other required elements are used to solve the problems
Solution Demo
Optional section showing screen shots and/or giving info on existing UMA-based implementations, deployments, etc. for addressing this problem