- WG-UMA - mailman.kantarainitiative.org

Reminder: UMA business-legal framework telecon 2019-12-10
by Eve Maler 09 Dec '19

09 Dec '19

We meet *8am PT* on Tuesdays at https://global.gotomeeting.com/join/857787301 -- see our calendar here <https://kantarainitiative.org/confluence/display/uma/Calendar>. Please see our notes page <https://kantarainitiative.org/confluence/display/uma/UMA+legal+subgroup+not…> for previous notes and handy links. We'll continue to work through our GDoc. Lisa and I have continued to make some edits. I think we're at the point of being able to introduce States other than #1 in the next section. :-) *Eve Maler*Cell or Signal +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl

1 0

Draft minutes of UMA telecon 2019-12-05
by Eve Maler 05 Dec '19

05 Dec '19

https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2019-12-05 MinutesRoll call Quorum was not reached. Approve minutes - - Approve minutes of UMA telecons 2019-10-03 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2019-10-03> , 2019-11-21 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2019-11-21> Deferred. Reminder: Identiverse CfP is open till Jan 10 Keep those cards and letters coming! Discuss recent next-gen authz news Adrian relates news from a symposium at which Thomas was presenting, where bots and swarms have roles to play, blockchain enables consensus on swarm activities, and there is a payment model for bots. Shades of (George's?) Device-Managed Access model and Ray Bradbury's Night Call, Collect <https://spilledthejillybeans.blogspot.com/2012/01/bradbury-friday-night-cal…>! And what if an intelligent machine ultimately infringes on an existing patent? The second decentralized identity meeting is tomorrow at 1pm ET. The minutes from the first meeting are here <https://docs.google.com/document/d/1wbaBx8p9Xe35IT4Lk4MnXAqzZ_ja68-9w7N8zkr…>. Planning for all this is happening on the DIF Slack workspace and also the W3C groups (there are at least three relevant ones; the most relevant is the Credentials Community Group <https://w3c-ccg.github.io/>). WGs are slightly more "closed". The calendar invitation is here <https://calendar.google.com/calendar/r/eventedit/copy/MjJmdHNucjQwYjJvYzlyb…>. Adrian's take: There are some people convinced and some not so convinced about Linked Data as a way to move forward. People representing (many) startups don't want to wait and want to press forward in Hyperledger Aries and(/or?) DIF. These two organizations seem friendly towards each other and MSFT is taking two steps back. Though Kantara has been mentioned and it hasn't been dismissed, it's unlikely. Adrian believes it's possible to accommodate a two-org track that continues with the W3C effort as well, e.g. with DIDcomm. Justin sees a challenge with the hard work of blocking and tackling of standards integration now needed. Adrian and others brought up UMA as a relevant technology/standard in the first meeting. A question of "IP" came up; apparently this has to do with the desire to build the decentralized web independent of TLS and basic lack of familiarity with Kantara and the existing standards world. Justin attended the side meetings on OAuth 2.1 (which weren't available for meetecho remote participation). If you have a 2.1 client talking to a 2.0 server with the right extensions, then everything should work fine; it adheres to semantic versioning (even though the WG hasn't made a formal commitment to semantic versioning overall). 2.1 is just a collection *and branding* of certain features like mandating auth code+PKCE etc. But it doesn't include extensions like RAR. He believes PAR is sufficiently baked to use, but RAR needs a lot more work. 2.1 could talk about dynamic client registration (DCR) but point off to sources. How do you deal with the need to constantly update security advice? Eventually you do issue a BCP for 2.1 if it's necessary. RAR/PAR is what has a few elements of UMA-relevant features. All along we've had a goal of "sedimenting" UMA features into OAuth itself, and been happy when this has happen, e.g., DCR. George sees the value of RAR as more than OAuth2. It's a JSON structure for dealing with internal microservice authorization issues. Eve had picked up on the fact that RAR enables resource-specific scopes in UMA-like fashion without requiring pre-registration of resources (as UMA does) in a specific resource owner context. UMA's protection API has the AS issue a resource ID that basically carries resource owner personal data because of that context. She believes Identos had created an UMA extension specifically to undo this bit of implication so as to privacy-enhance AS interactions – is that so? Adrian asks about a RAR/PAR relationship to ZCAP <https://w3c-ccg.github.io/zcap-ld/> (the Linked Data spec at W3C); Justin believes they're not related. Maybe we can drill down into the topic of DCRs and different types of wide ecosystem a bit more. Attendees As of 16 Jul 2019, quorum <https://kantarainitiative.org/confluence/display/uma/Participant+Roster> is 5 of 9. (Domenico, Peter, Sal, Thomas, Andi, Maciej, Eve, Mike, Cigdem) 1. Domenico 2. Andi 3. Eve 4. Mike Non-voting participants: - Adrian - George - Scott - Bjorn - Justin Regrets: - Maciej *Eve Maler*Cell or Signal +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl

1 0

Agenda for UMA telecon 2019-12-05
by Eve Maler 04 Dec '19

04 Dec '19

(In keeping with recent tradition, this agenda is a bit informal.) Let’s continue the discussion of “XYZ/RAR/PAR” by catching up on IETF 106 Singapore goings-on, and also the decentralized identity meeting(s?). Eve Maler (sent from my iPad) | cell +1 425 345 6756

1 0

Notes from 2019-12-03 UMA business-legal framework telecon
by Eve Maler 03 Dec '19

03 Dec '19

Great session, thanks everyone! https://kantarainitiative.org/confluence/display/uma/UMA+legal+subgroup+not… 2019-12-03 Attending: Eve, Domenico, Lisa, Nancy (regrets: Tim) Lisa's and Eve's "Beyond Consent" article is now in a near-final version; Lisa kindly agreed (when asked by Eve) to distribute this version to the UMA WG. *Consensus:* We looked at the Typical Use Case section of the doc and concluded that we do like having the "typical use case" for technical roles presented, followed by the formal definitions of said roles. Let's also plan to publish the spreadsheet as a companion Report because it can serve as the "source of truth" of definitions and relationships. We can prepare an Annex or Appendix or whatever we want to call it in this Report that consists of tables, along with a citation to the spreadsheet that has "live" data. We can say "In case of any discrepancy, the spreadsheet has the most accurate data" etc. *Assumption:* We note here – but don't want to note in the Report, because it would complicate things for the readers – that EHR data typically gets selectively copied to a portal, and doesn't "live" there. If we elucidated all of our assumptions and caveats in the "typical use case", we'd never get anywhere. Nancy is clarifying for our group exactly how SMEs would split hairs on primary storage of health data. We agree that our audience will be motivated simply to understand the UMA paradigm at a relatively high level at this stage. Lisa asks (paraphrased): When we say the resource owner "manages" resources at the RS and "controls" access at the AS, is she doing that at an app of some sort? Why are we saying Alice is interacting directly with services here and not apps? She does use apps, but we don't talk about them in protocol-related conversations because those interactions aren't "on the wire"; there are no UMA-dictated messages involved. However, those who deploy UMA-enabled systems do have to concern themselves with the implementation and deployment of such apps! Eve's recent webinar with Steve Giovannetti covered the four elements of integration and deployment needed: - Deploy an AS. We have noted many times that policy engine functionality is something each AS can compete on because it lets ROs get more sophistication in policy-setting ability. However, often in healthcare use case conversations, the idea of policy interoperability comes up too. - Integrate/create your client app (if you already have a client, you have to UMA-enable it) – is there room for creating "UMAlet" middleware? Gluu has talked about its open-source middleware in the past. - Deploy your RS (if you already have RS apps, you need to UMA-enable them) – there are a couple of different approaches, gateway/proxy (could be in the cloud) and an SDK for UMA-enabling apps. The former seems preferred. Eve calls these "protectlets" [image: (smile)]. - Encourage data partners to implement their own RS's – if you have a wide data ecosystem (i.e., multiple RS's in different domains), your partners will have to UMA-enable their hosts. Helping them do this is good business! See just above. Nancy notes that Patient Centric Solutions' new PatientShare offering does exactly this. This whole list opens up the idea of publishing an auxiliary document called something like an *UMA Deployment Guide* and stimulating open source (once more) to encourage deployments. *Proposal:* Lisa suggests that, since the Operators are extremely likely to be Legal Persons, we should acknowledge the obvious and enhance the formal definitions in the document somehow so that it won't trip up people who read them there. Maybe we can insert some bracketed text and/or italicize some? She will draft some candidate text and let's discuss it on the list. There are so many considerations around this question – rhetorical, UMA maturity, etc., that it's not even funny. Domenico comments on the concept of a "data ecosystem". We've been talking about wide ecosystems for a while, but it seems there are different kinds of wide ecosystems. Lisa says: "UMA is an ecosystem builder." Nice! Eve has often called OAuth2 a protocol framework because it has so many choices that it's not just one protocol; unfortunately that has risked interoperability and security. XYZ is trying to enable protocol-building without all those sacrifices. UMA is meant to make it possible to build data – and data-sharing – ecosystems without sacrifices and compromises. *Eve Maler*Cell or Signal +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl

1 0

Paper "Beyond Consent: A Right-to-Use License for Mutual Agency"
by Lisa LeVasseur 03 Dec '19

03 Dec '19

Hi folks, Here's the latest version of the paper Eve mentioned today. Lisa

1 0

Reminder: UMA business-legal telecon 2019-12-03
by Eve Maler 02 Dec '19

02 Dec '19

(December already??) We meet 8am PT on Tuesdays at https://global.gotomeeting.com/join/857787301 -- see our calendar here. Please see our notes page for previous notes and handy links. We'll continue to work through our GDoc. Eve Maler (sent from my iPad) | cell +1 425 345 6756

1 0

Just posted a new implementation on our Implementations page!
by Eve Maler 23 Nov '19

23 Nov '19

Nancy sent me news of an UMA implementation her company has done -- you can read about it here: https://kantarainitiative.org/confluence/display/uma/UMA+Implementations#UM… @UMAWG is spreading the news and it's also on our wiki home page. Will you help out? Thanks in advance! https://twitter.com/UMAWG/status/1198015446475296768 (BTW, happy Thanksgiving to everyone who is celebrating it next week.) *Eve Maler*Cell or Signal +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl

2 1

Draft minutes of UMA telecon 2019-11-21
by Eve Maler 21 Nov '19

21 Nov '19

https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2019-11-21 MinutesRoll call Quorum was not reached. Approve minutes - - Approve minutes of UMA telecon 2019-10-03 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2019-10-03> Deferred. Decentralized news Adrian has news to share; see his document <http://bit.ly/MVProtocol>. Eve has been working on an article with Lisa L on consent, and they have struggled with the lack of concrete flows in decentralized identity for consent. George concurs with the lack of concreteness out there; it's a problem for interoperability with DID methods to date. Adrian notes that there is an open meeting planned for tomorrow <https://lists.w3.org/Archives/Public/public-credentials/2019Nov/0037.html> to discuss (meta-discuss?) how to get started in bringing all the various streams of work to standards bodies. Resolving DIDs and telling wallets what VCs you want and other use cases will rely on commonality communications. It's possible to build POCs to illustrate concepts, but it doesn't build ecosystems. We walked through Adrian's document. It focuses on the Alice-to-Bob use case to keep things simple (UMAnitarians are very familiar with that). Alice-to-Alice is just a subset. MVP (minimum viable protocol) is represented by the "narrow waist" of the hourglass. Slide 5 introduces an UMA mapping to the entities. Slide 7 makes the resource owner their own issuer, interestingly. The hot conversation in the decentralized community is the two data storage options on slide 8; the bold elements are the complementary strengths on either side, the goal being to not be stuck with just Apple or Google as the wallet choice. Some discussion ensued about the larger ecosystem/adoption questions surrounding how to privacy-engineer personal data choice and control. Eve shared Bob Blakley's remarks from TechVision Chrysalis on decentralized identity about wallet binding/"evil Alice" concerns (which Eve supported contemporaneously). XYZ / RAR / PAR news Eve described the OAuth 2.1 proposal from the IETF 106 OAuth 1 session and its enthusiasm for code+PKCE (and a further set of protections). George is concerned about this being insufficient for mobile wallet-binding protection. Adrian echoes this concern. How to ensure trust when talking to the correct client (instance, not just class)? Currently, RAR (along with PAR) is designed to be a relatively lightweight extension on top of today's OAuth. In OAuth, Alice is sent to her bank/ASPSP (AS) to authorize or deny the transaction. In UMA, how would the AS know how to let Alice set her policy, which would be the equivalent operation? That's why we had a resource (and scope) registration step ahead of time. The fact that pre-registration was in the RO context was beneficial (essential) for the various parts of the flow/token ecosystem of UMA. But maybe we can use the RAR JSON data structure to inform our registration step. George says he's "stealing" that structure for what he calls transaction tokens, for internal microservices management. Attendees As of 16 Jul 2019, quorum <https://kantarainitiative.org/confluence/display/uma/Participant+Roster> is 5 of 9. (Domenico, Peter, Sal, Thomas, Andi, Maciej, Eve, Mike, Cigdem) 1. Domenico 2. Maciej 3. Eve 4. Cigdem Non-voting participants: - Adrian - George - Scott - Thomas - Nancy Regrets: - Peter *Eve Maler*Cell or Signal +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl

1 0

Planning for Thursday's UMA WG call
by Eve Maler 20 Nov '19

20 Nov '19

As my recent note mentioned, the plan is to have an UMA WG "technical" call this Thursday. I'd like to discuss the RAR/PAR specs particularly, since we haven't fully yet, and catch up on XYZ. Here is the previous thread discussing RAR <https://groups.google.com/forum/#!topic/kantara-initiative-uma-wg/56_fskNkn…>, and here is a handy IETF 106-related blog post <https://oauth.net/events/2019-11-ietf106/> with relevant spec links. (I attended the TXAuth BOF session remotely and plan to dial in to OAuth session 1 tonight.) If we meet, will we have sufficient attendees to have an interesting conversation? Please send a note in this thread or on Skype if you can make it. Thanks. *Eve Maler*Cell or Signal +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl

1 1

Upcoming UMA WG meetings
by Eve Maler 17 Nov '19

17 Nov '19

Hi all– I need to make some adjustments to upcoming UMA telecons due to shifting schedules. Here is the plan for the rest of the calendar year. Don't forget you can ask to receive a calendar invitation if you aren't already on them. Tuesday 8am PT meeting series (business-legal framework, goal: draft second report): - Tue Nov 19: *need to cancel (new)* - Tue Nov 26: canceled due to US holiday - Tue Dec 3: meeting - Tue Dec 10: meeting - Tue Dec 17: *I need to shift this a half-hour earlier due to an interfering meeting* - Tue Dec 25: will cancel due to holiday - Tue Dec 31: will cancel due to holiday Thursday 6am PT meeting series (technical, main goals: extension/XYZ use case collection, charter refresh): - Thu Nov 21: meeting - Thu Nov 28: canceled due to US holiday - Thu Dec 5: meeting - Thu Dec 12: meeting *(will call for agenda items and may cancel if none)* - Thu Dec 19: meeting *(will call for agenda items and may cancel if none)* - Thu Dec 26: will cancel due to holiday - Thu Jan 2: will cancel due to holiday *Eve Maler*Cell or Signal +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl

1 0