...
- Thursdays, 9-10am PT
- Screenshare and dial-in: http://join.me/findthomas
- UMA calendar: http://kantarainitiativekantara.atlassian.orgnet/confluencewiki/display/uma/Calendar
Agenda
Roll call
Approve minutes of UMA telecon 2017-06-29
- Public Comment/IPR Review period concluded on July 12 at 11:59 UTC
- UMA V2.0 work:
- All GitHub issues for V2.0/Grant swimlane, FedAuthz swimlane/Release Notes/UIG/Wikipedia
- Issues #326-#330 have been implemented
- Please check out draft solution for #328: how client-contributed scopes are mapped to resources during authorization assessment
- Let's briefly discuss #334: the IANA registration request for the JWT
permissionsclaim and its constituent parts - Several of the items in #337 are worth discussing
- If you want to review and weigh in on the other public-comment-period issues, please do it before the call
- Release notes are getting more fleshed out; review (and contributions) welcome
- Finalizing the specs
- When will we be ready to vote on progressing specs to the LC and then to All-Member Ballot?
- UMA2 logo ideas
- AOB
...
Approve minutes of UMA telecon 2017-06-29: Deferred.
UMA 2.0 work
#328: how client-contributed scopes are mapped to resources during authorization assessment: Eve's first iteration was "Treat each scope in (ClientRequested ∩ ClientRegistered) as applying to all matching resource-bound scopes in PermissionTicket." She's thinking that it would be more accurate to say something like "...all scopes associated with resources appearing in PermissionTicket", and then we could add ", with the scope matching performed as described in Section 6.2.1 of [RFC3986] (Simple String Comparison)."
...
Eve speaks in favor of option 1 (EDIT: originally said 2; should have said 1). Kathleen notes that it's good to keep solving this properly on the roadmap. Sal agrees. James agrees. We have consensus.
...