1. User-Managed Access UMA Work Group @UMAWG tinyurl.com/umawg | tinyurl.com/umafaq IIW 16, May 2013 1

2. The “data price” for online service is too high: typing… Provisioning by hand Provisioning by value Oversharing Lying! 2

3. The “data price” for online service is too high: connecting… Meaningless consent to unfavorable terms Painful, inconsistent, and messy access management Oblivious oversharing 3

4. The “data price” for online service is too high: private URLs… Handy but insecure Unsuitable for really sensitive data 4

5. 5 Most data “sharing” today is back-channel and unconsented Image source: http://informationanswers.com/?p=283

6. Privacy is about context, control, choice and respect – so UMA enables a “digital footprint control console” Web 2.0 access control is inconsistent and unsophisticated To share with others, you have to list them literally You have to keep rebuilding your “circles” in new apps You can’t advertise content without giving it away You can’t get a global view of who accessed what You can unify access control under a single app Your access policies can test for claims like “over 18” You can reuse the same policies with multiple sites You can control access to stuff with public URLs You can manage and revoke access from one place 6

7. UMA turns online sharing into a privacy-by-design solution Historical Municipal Financial Vocational Artistic Social Geolocation Computational Genealogical Biological Legal... Historical Municipal Financial Vocational Artistic Social Geolocation Computational Genealogical Biological Legal... 7

8. UMA turns online sharing into a privacy-by-design solution I want to share this stuff selectively Among my own apps With family and friends With organizations I want to share this stuff selectively Among my own apps With family and friends With organizations I want to protect this stuff from being seen by everyone in the world 8

9. UMA turns online sharing into a privacy-by-design solution 9 I want to control access proactively, not just feel forced to consent over and over

10. UMA is a profile of OAuth, with bits added for interop and scale 10 resource owner resource server authorization server client protecte d resource s (unnamed till now)

11. UMA solves for 1) individual choice and 2) fully modular cloud services 11 App-specific API UMA-enabled client RPT requesting party token

12. UMA solves for 1) individual choice and 2) fully modular cloud services 12 Protection API Protection client PAT protection API token includes resource registration API and token introspection API

13. UMA solves for 1) individual choice and 2) fully modular cloud services 13 Authorization API Authorization client AAT authorization API token supports OpenID Connect-based claims-gathering for authz

14. Key use cases http://kantarainitiative.org/confluence/display/uma/Case+S tudies http://kantarainitiative.org/confluence/display/uma/Case+S tudies Subscribing to a friend’s personal cloud Sharing accessibility attributes (“GPII”) E-transcript sharing (“HEAR”) Patient-centric health data access Enterprise “access management 2.0” 14

15. Key implementations http://kantarainitiative.org/confluence/display/uma/UMA+Implementatio ns http://kantarainitiative.org/confluence/display/uma/UMA+Implementatio ns SMARTAM.net (running authorization service from Cloud Identity UK) Puma (Python libraries for RS- and client- enabling web apps) from ditto Fraunhofer AISEC open- source implementation in Java Gluu OX open-source implementation for Access Management 2.0 use cases 15

16. Next steps Work on optimization opportunities when UMA and OpenID Connect are used together Issue “Implementor’s Draft” Continue to work with AXN, Scalable Privacy, and others in “trusted identities in cyberspace” ecosystem Profile UMA for higher ed, accessibility attribute sharing, healthcare use cases We welcome your involvement and contributions –Become an UMAnitarian! –Follow @UMAWG on Twitter and UserManagedAccess on FB 16

17. Questions? Thank you @UMAWG tinyurl.com/umawg | tinyurl.com/umafaq IIW 16, May 2013 17

18. Phase 1: protect a resource 18

19. Phases 2 and 3: get authorization and access resource 1 of 3 19

20. Phases 2 and 3: get authorization and access resource 2 of 3 20

21. 21 Phases 2 and 3: get authorization and access resource 1 of 3

22. Spec call tree for the UMA profile of OAuth 22 UMA coreOAuth 2 OpenID Connect Token introspection OAuth resource set registration UMA binding obligations Dynamic client registration hostmeta UMA native spec Required external component Optional external component Individual IETF I-D