December 2015 - WG-UMA - mailman.kantarainitiative.org

Documenting UMA publication workflows
by Eve Maler 18 Jul '16

18 Jul '16

Hi folks-- Hope you are enjoying post-Christmas reentry or more holiday time, or whatever the case may be. Maciej and I are working on publishing the new Recommendations, and due to that, I unearthed the permanent/symbolic link information that I promised to Justin; we thought it would be a good idea to document the processes here -- and in the GitHub readme... It seems to work pretty well for now given that there isn't that much to the entire publishing process for our WG or others, but if you see ways to improve it for the future, let us know. After completing a draft spec revision cycle and getting it approved: 1. Edit the draft-uma-core-vn_n[_n] and draft-oauth-resource-reg-vn_n[_n] sources to change from Status #3 to #4 (see below), leaving the previous date in place. 2. Run the stylesheet over the XML sources to produce .html outputs, review the results as required, sync GitHub, and upload the last drafts by FTP (Eve and Oliver can do this). 3. Save the draft-uma-core-vn_n[_n] and draft-oauth-resource-reg-vn_n[_n] sources off to new files in the repo starting with rec- instead. 4. Change the Status section of the new files from #4 to #5, the date, and any other metadata (some of this has to be done in the stylesheet, which is in the repo). 5. Update the two specs' References links to each other in the Reference section. 6. Run the stylesheet over the XML sources to produce HTML output with .html extensions, review the results as required, sync to GitHub, and FTP the HTML results to the website (Eve and Oliver can do this). 7. Get symbolic links created (see below) from the versioned rec- HTML links to generic links (Oliver can do this). After launching a new draft spec revision cycle: 1. Save the rec-uma-core-vn_n[_n] and rec-oauth-resource-reg-vn_n[_n] sources off to new files in the repo starting with draft- and having the agreed new version numbers instead. 2. Edit the Status section from #5 to #1. 3. Proceed to edit the new drafts, and periodically produce HTML results that can be uploaded through FTP. 4. Get symbolic links created from the versioned draft- HTML links to generic links (Oliver can do this). Here are the stages of the Status section (embed links throughout as appropriate): 1. This document is a draft technical specification produced by the User-Managed Access Work Group <http://kantarainitiative.org/confluence/display/uma/Home>. 2. This document is a Kantara Initiative Draft Recommendation approved by the User-Managed Access Work Group <http://kantarainitiative.org/confluence/display/uma/Home>. 3. This document is a Draft Recommendation approved by the User-Managed Access Work Group <http://kantarainitiative.org/confluence/display/uma/Home> and certified by the Leadership Council to undergo a Kantara All-Member Ballot. 4. This document is a Draft Recommendation approved by the User-Managed Access Work Group <http://kantarainitiative.org/confluence/display/uma/Home> and certified by the Leadership Council to undergo a Kantara All-Member Ballot. The Ballot having passed, this document has been superseded by the Recommendation version of the document. 5. This document was developed by the User-Managed Access Work Group <http://kantarainitiative.org/confluence/display/uma/Home> and approved by the Membership of the Kantara Initiative <http://kantarainitiative.org/> as a Recommendation. Here is how the symbolic links work: https://docs.kantarainitiative.org/uma/rec-uma-core-vn_n[_n].html - Permanent link to specific Core Rec https://docs.kantarainitiative.org/uma/rec-oauth-resource-reg-vn_n[_n].html - Permanent link to specific RSR Rec https://docs.kantarainitiative.org/uma/draft-uma-core-vn_n[_n].html - Permanent link to specific Core Rec https://docs.kantarainitiative.org/uma/draft-oauth-resource-reg-vn_n[_n].ht… - Permanent link to specific RSR Rec https://docs.kantarainitiative.org/uma/rec-uma-core.html - Symbolic link to latest Core Rec https://docs.kantarainitiative.org/uma/rec-oauth-resource-reg.html - Symbolic link to latest RSR Rec https://docs.kantarainitiative.org/uma/draft-uma-core.html - Symbolic link to latest Core draft https://docs.kantarainitiative.org/uma/draft-oauth-resource-reg.html - Symbolic link to latest RSR draft *Eve Maler*Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl

1 2

Ideas for an UMA extension for shorter flow
by Mike Schwartz 06 Jan '16

06 Jan '16

Uma-tarians, Here at Gluu we've been trying to come up with some options for API access management that leverage our UMA capabilities, while reducing the number of steps associated with the permission ticket flow. We came up with three options: 1) Eagerly issue an RPT token with permissions for resource sets where all scopes are satisfied. 2) Create a new token which just has the expiration and a list of scopes. Something like: { "active": true, "exp": 1256953732, "iat": 1256912345, "permissions": ["view", "manage" ] } And then the RS can evaluate if these scopes are sufficient for access. Maybe this token can be called the EAT (eager access token) or the GST (Granted Scope Token). 3) The RS takes the token above, and uses the OAuth2 token exchange endpoint, (see draft: https://tools.ietf.org/html/draft-ietf-oauth-token-exchange-03 ) to swap out for a real RPT that specifies the scopes, or returns a permission ticket as normal if the scopes aren't suffcient. #1 has scale problems... especially if the AS has resource sets registered by RS's in many domains. It seems only appropriate for very small deployments in a single domain. #2 has minimal overlap with UMA. #3, I guess you have to wonder if it is really much better than the permission ticket flow. It moves complexity to the client, and in a best case, saves two steps (obtaining permission ticket, returning permission ticket). - Mike ------------------------------------- Michael Schwartz Gluu Founder / CEO mike(a)gluu.org

4 9

Happy Holidays and Happy New Year!
by Eve Maler 25 Dec '15

25 Dec '15

A very quick update... Just wanted to let you know that our All-Member Ballot for the V1.0.01 specs passed with 25 Yes votes and no No votes. We required at least 10 votes total, with 8 of them being positive. Great show of support, and great GOTV effort; thanks to you, to Jane and the rest of the Kantara staff, and to the Kantara community at large! Talk to you all on the flip side :-), Eve *Eve Maler*Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl

1 0

Thoughts on Obligations
by Allan Foster 23 Dec '15

23 Dec '15

Folks, I am concerned about putting specific obligations on the RS and thus subjagating it to the AS. Specifically to allow for Enterprise MAC with UMA participation, where the End user is a participant in the access control decision, but not the only participant. 1. *Resource Server Operator <http://www.commonaccord.org/index.php?action=source&file=GH/KantaraInitiati…>-Authorizing Party <http://www.commonaccord.org/index.php?action=source&file=GH/KantaraInitiati…>: Delegate-Protection* For the period that the Resource Server Operator <http://www.commonaccord.org/index.php?action=source&file=GH/KantaraInitiati…> and Authorizing Party <http://www.commonaccord.org/index.php?action=source&file=GH/KantaraInitiati…> have mutually agreed to serve in these respective roles for each other, theResource Server Operator <http://www.commonaccord.org/index.php?action=source&file=GH/KantaraInitiati…> gains an obligation to the Authorizing Party <http://www.commonaccord.org/index.php?action=source&file=GH/KantaraInitiati…> to delegate protection services to the Authorization Server Operator <http://www.commonaccord.org/index.php?action=source&file=GH/KantaraInitiati…> for the set of protectable resources for which it represents this capability to the Authorizing Party <http://www.commonaccord.org/index.php?action=source&file=GH/KantaraInitiati…>, and to respect the authorization data that the Authorization Server <http://www.commonaccord.org/index.php?action=source&file=GH/KantaraInitiati…> has associated with an RPT <http://www.commonaccord.org/index.php?action=source&file=GH/KantaraInitiati…> when the Resource Server <http://www.commonaccord.org/index.php?action=source&file=GH/KantaraInitiati…> subsequently allows or disallows access by the Client <http://www.commonaccord.org/index.php?action=source&file=GH/KantaraInitiati…> that presented that RPT <http://www.commonaccord.org/index.php?action=source&file=GH/KantaraInitiati…>. My concern here is that it delegates "Protection services" to the AS, and this feels a little like an all or nothing. This might not be true in the case where the RO is only one party in the Access control decision. 3. *Resource Server Operator <http://www.commonaccord.org/index.php?action=source&file=GH/KantaraInitiati…>-Authorization Server Operator <http://www.commonaccord.org/index.php?action=source&file=GH/KantaraInitiati…>: Respect-Permissions* For the period that the Resource Server Operator <http://www.commonaccord.org/index.php?action=source&file=GH/KantaraInitiati…> and Authorization Server Operator <http://www.commonaccord.org/index.php?action=source&file=GH/KantaraInitiati…> have mutually agreed to serve in these respective roles for each other, the Resource Server Operator <http://www.commonaccord.org/index.php?action=source&file=GH/KantaraInitiati…> gains an obligation to the Authorization Server Operator <http://www.commonaccord.org/index.php?action=source&file=GH/KantaraInitiati…> to disallow access by a Client <http://www.commonaccord.org/index.php?action=source&file=GH/KantaraInitiati…> presenting an RPT <http://www.commonaccord.org/index.php?action=source&file=GH/KantaraInitiati…> in all cases where the authorization data associated by the Authorization Server <http://www.commonaccord.org/index.php?action=source&file=GH/KantaraInitiati…> is insufficient for the access attempt.. The RS is obligated to dissallow access in the AS cannot provide sufficient rights - in all cases. This has several implications. If the RS has additional business rules whereby a party might get access even tho they are not UMA authorized, (break glass?) (Admin or Help Desk) The RS HAS to determine if a user is a special user BEFORE making the request to the AS. Since once it has an answer, it is obligated to deny. This implies that the RS cannot opt out once the request to the AS is made. It feels a little bit like don't ask don't tell! My Concern is that the RS is ALWAYS the final arbitrator of access control, whether UMA, DAC or MAC. It should be able to modify its behavior based on local business rules and exceptions. Allan -- Simplify Email: Email Charter <http://emailcharter.org/> ForgeRock Logo *Allan Foster - ForgeRock * /VP Strategic Partner Enablement/ *Location:*San Francisco *p:* +1.214.755.9218 *email:* allan.foster(a)forgerock.com <mailto:allan.foster@forgerock.com> *blogs:* blogs.forgerock.com/GuruAllan <http://blogs.forgerock.com/GuruAllan> *Skype:* Call GuruAllan <http://is.gd/lWVfMG> *www:* www.forgerock.com <http://www.forgerock.com/> *www:* www.forgerock.org <http://www.forgerock.org/>

5 8

Two thoughts for UMA enhancments
by Mike Schwartz 22 Dec '15

22 Dec '15

UMA-tarians, Can we discuss two ideas for enhancments: 1) UMA sans permission ticket Let's say the UMA Client knows the scopes required to call a certain API. For example, Google documents this: http://gluu.co/google-scopes In this case, perhaps the client can proactively request an RPT providing the scopes. And this RPT might be acceptable a certain RS for certain resource sets. We might have already discussed this, but wouldn't this make UMA more compatable with existing API access management infrastructures? 2) UMA without the AAT Inspired by Justin. I think the AAT adds value in many cases where the AS wants to make policies based on client claims (client id, domain specific catagory, etc). So I'm not saying eliminate the AAT. However, if the policy for access is based on network address only, or perhaps some other fraud detection technique that doesn't involve client identification, I could see a case where the AAT is not needed. So maybe the AAT could be optional? - Mike ------------------------------------- Michael Schwartz Gluu Founder / CEO mike(a)gluu.org

7 20

Notes from UMA legal subgroup telecon 2015-12-18
by Eve Maler 22 Dec '15

22 Dec '15

- Review the first draft deliverable <http://www.commonaccord.org/index.php?action=doc&file=GHx/KantaraInitiative…> and its model clauses and definitions - How to take our work forward? Continue our subgroup meetings? - AOB Attending: Eve, Andrew H, Steve, Adrian, John W, Mark, Ann, Jon N, Jim, Scott, Dazza *How to take our work forward? Continue our subgroup meetings?* What is the interest in continuing the subgroup meeting series into 2016? Andrew is interested in a capped-length subgroup meeting series, e.g. six months tied to outcomes, but is wary of scope drift. Adrian would like to see an implementation group continue, but he's wondering where the academic focus went. Eve described the 2015 mission <http://www.commonaccord.org/index.php?action=doc&file=GHx/KantaraInitiative…> as relentlessly practical. Mark noted that with the consent receipt work pushing forward, the direction of this work and further collaboration seem very important. Eve will propose a fresh, limited draft charter for the subgroup. Eve will schedule a meeting on Friday January 8 for us to review where we are for the first half of 2016. *Review the first draft deliverable and its model clauses and definitions* *Intro first para:* We suggest Jim and Scott follow up to switch to "represent" language vs. declaration and conformance (only "operators" can conform, vs. "users"). *Does the color marking system work?* Andrew suggests that color coding doesn't help for tokens. But for defined terms and abbreviations, it does, and probably for the persons/parties. *Idea for the UX:* It would be cool if clicking on a term/abbreviation would take the reader to the definition. *What to do about Individual/NPE/Subject?* In the era of IoT, we have to get this very right. The alternative that would be both legal- and technical-friendly would be *Individual *(?)*/Legal Person/* Device/Application/etc.*/Person*. Note that Subject in a legal sense is much more than "subject" in a technical sense; the former is the "subject of someone's gaze" (think data subject) and the latter, at least in security and identity is the subject of authentication. Also, we'll need conversion tables into other natural languages. Can we define the terms as bounded by US law until we can vet that it works cross-jurisdictionally, or provide sets of terms that are compatible with different jurisdictions? If we're targeting Canada as a first "customer", how should we handle this? Maybe we can put a note into the relevant definitions, we can put in notes about these being derived from US law. Can we borrow/steal from some existing federation language to support our UMA-specific needs? The UETA may have everything we need to support both "bags of protoplasm" and "organizations" running "server-side services" and "client-side apps". Jim will propose a change to this set of terms, with Legal Person (without an abbreviation). We may someday use NPE for equipment. *Two-party or three-party relationships?* We can see three-party relationships we clustering of two-party relationships, where a condition precedent to one two-party relationship is the formation of a prior two-party relationship. We can state any condition precedent and/or condition subsequent in terms of UMA roles (and leave holes for non-UMA conditions). AI: Jim/Eve: We'll have to be sure to do that in our clause reusability structuring. Scott notes that there's an RNA analogy. And Dazza notes that the Carat Guidelines from the '90s (here <http://civics.typepad.com/files/carat_final_011400-1.pdf>) said that there should be a limited number of roles, functions are allocated to roles, and when there are permutations and functions are allocated to more than one legal party, it should be clear what rights and obligations are delegated to them and which are delegable and non-delegable. Maybe we can include some of that language! *Adrian's earlier comments:* In email, Adrian sent comments that pointed out a typo we will fix. *Analyzing the very first clause:* "When the Client successfully gains access from a Resource Server to a protected resource by wielding a valid "bearer" RPT associated with at least one currently valid permission for the type of access sought, the Requesting Party using that Client gains an obligation to the Authorizing Party to adhere to any terms it agreed to in order to gain the permission." We drilled down into the specific Adhere-to-Terms clause source <http://www.commonaccord.org/index.php?action=source&file=GHx/KantaraInitiat…>, which has "comments" and "issues" that don't show up in the main document rendering. Eve observes that: - A LOT of conditions precedent seem to be buried in that one condition! - We probably need to get into the weeds of the Client Operator in a way we haven't previously. - We haven't said that the Requesting Party actually supplied claims, and maybe this Duty should only depend on a Condition of having supplied claims; the Issue mentions that the Condition perhaps be at the juncture of supplying the claim. - And oh, by the way, this clause is just stating the "blinding flash of the obvious" about what the protocol messages *exist to mean*. SAML the protocol never ever stated this: An IdP never promises to mean that it authenticated somebody at time *x* using method *y*. Scott observes that: - Right. Sit down in the chair -- get a haircut -- you have to pay for it. :-) Dazza observes that: - We have to get into "all applicable laws need to be followed". - We can start to have everyone propose clauses for our "clause bank", now that we are hammering out the canonical form. Jim observes that: - We can actually have a series of "Duty" phrases that can appear as alternatives and/or can aggregate. This would be a different reusability logic vs. the Adhere-to-Terms unique naming of each Duty, and would depend on whether the Condition is unique per set of Duty phrases. Jim and Eve: Propose a fresh clause skeleton <http://www.commonaccord.org/index.php?action=source&file=GHx/KantaraInitiat…> . *Thanks to all, with especial thanks to Jim and Mark! See you on the other side!* *Eve Maler*Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl

2 7

UMA MVP for IoT
by Adrian Gropper 22 Dec '15

22 Dec '15

To help make UMA easier to understand and adopt, I'd like to propose a very simple IoT use-case. As background, check out the 1:23 video of McAffe pitching EveryKey. https://www.indiegogo.com/projects/everykey-your-only-key#/ What would this look like if all the locks, keys, and authorization servers were totally UMA standard and cost around $30? The use-case is pretty simple: - A door lock is a Non-Person Entity. It's the UMA Resource Server and, in addition to Resource Registration, it typically executes three commands: Register Key, Unlock Door, and De-register Key. The Resource Server Operator (RSO) is a home or office entity. - A key is an UMA Client, typically associated with a single person that might live in the home (Alice) or might visit occasionally (Bob). The key has two "buttons" labeled Register and De-Register. We make the assumption that all locks within a couple of feet unlock by proximity and that Register and De-Register add some kind of pairing dance such as a button and light on the lock and key. - Alice lives in the home and has an UMA Authorization Server. Alice's AS is generic and doesn't know anything specific to locks. Alice doesn't share her AS with her roommates. Alice is able to register her AS with the lock by authenticating with the RSO in-person. - Alice is now able to enable access by her friend Bob by sending to his smatphone an invitation email or text pointing to her unlock resource on the lock. Bob will use his Bluetooth key and his smartphone to register with Alice's AS and gain access. If Alice's AS happens to be nearby, this use-case might happen entirely over Bluetooth with no connection to the Internet. In this case, the status of the SSL certificates cannot be checked but everything should work. Other than the SSL certificates such as Let's Encrypt, this use-case leaks no private data to the cloud or to any external entities. The lock, the key, and Alice's AS are all assumed to be separate open source technologies. There are bilateral contracts between the operators of the lock (RSO), Alice as the AS operator (ASO), and Bob as responsible for the key (RqP). These contracts must all include a provision for Notice to the counter-party of the contract if the lock, AS, or key are lost or otherwise compromised. Ideally, each of the three technology actors (lock, key and AS) in this use-case could be a C.H.I.P. https://en.wikipedia.org/wiki/Next_Thing_Co. (It would be better if CHIP included a secure element, but that's a peripheral issue). Adrian <http://patientprivacyrights.org/donate-2/>

2 9

Reminder: UMA legal subgroup telecon 2015-12-18 (90 minutes; last meeting of 2015; please attend!)
by Eve Maler 16 Dec '15

16 Dec '15

*Please try and attend this one!* You will see candidate model clauses that need your review and input. Thank you! - *Fri Dec 18 8-9:30am PT (90 minutes)* - Voice: Skype: +99051000000481 or US +1-805-309-2350 (international dial-in lines <https://www.turbobridge.com/join.html>), room code 178-2540# - Screen sharing: http://join.me/findthomas - *NOTE:* *IGNORE* the join.me dial-in line shown here in favor of the dial-in info above (Kantara "line C" and the Skype line) - UMA calendar: http://kantarainitiative.org/confluence/display/uma /Calendar - Review the first draft deliverable <http://www.commonaccord.org/index.php?action=doc&file=GHx/KantaraInitiative…> and its model clauses and definitions - How to take our work forward? Continue our subgroup meetings? - AOB *Eve Maler*Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl

1 0

News from the Kantara board
by Eve Maler 16 Dec '15

16 Dec '15

https://kantarainitiative.org/an-announcement-from-the-kantara-board/ *Eve Maler*Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl

1 0

Action request: Review by Friday's UMA legal subgroup meeting
by Eve Maler 16 Dec '15

16 Dec '15

Jim Hazard and I have been working assiduously to prepare a *draft UMA legal deliverable* for you all. It's not very long, but it's got a lot of interesting "guts" (which you don't have to look at if you're squeamish :-). Particularly if you're a legal subgroup, *please* fix yourself a nice beverage, click over to this document <http://www.commonaccord.org/index.php?action=doc&file=GHx/KantaraInitiative…>, and settle in for about an hour's worth of *review and commenting* before our Friday meeting. Read the introductory section to understand what you're looking at and what to review for. If you're rusty on UMA particulars, you can look at the older Binding Obligations <http://docs.kantarainitiative.org/uma/draft-uma-trust.html> document and its links for context -- or feel free to *ping me with questions*. *Thank you very much* in advance for contributing to this important milestone! I'll send a formal agenda later today, but *please mark your calendar* for a 90-minute last-of-2015 legal subgroup call on Friday. Talk to you soon! *Eve Maler*Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl

1 0