UMA telecon 2014-07-03

Owned by Eve Maler
Last updated: Jul 03, 2014
4 min read

UMA telecon 2014-07-03

Date and Time

Agenda

  • AI status
    • Excerpting the demo portion of the webinar recording
    • Outreach to webinar attendees
    • Editorial updates to drafts to ready them for public review
    • Others?
  • Upcoming events
    • CIS: UMAnitarian BOF?
    • SURFnet Kantara workshop ~Sep 4
  • Discuss healthcare use cases
    • Surface some of the email discussion of recent weeks
  • Editors' ad hoc meeting to edit specs into shape
    • Assuming at least Thomas and Maciej are available
    • Others can drop at this point if they like
  • AOB

Minutes

AI status

  • Excerpting the demo portion of the webinar recording
  • Outreach to webinar attendees
  • Editorial updates to drafts to ready them for public review
  • Others?

Thomas found a Windows-only tool that enables conversion of WebEx recordings into something more standard. He'll play with the excerpting process within the next week.

AI: Eve: Arrange to get an email sent to all webinar attendees with the recording and slide links.

Upcoming events

  • CIS: UMAnitarian BOF?
    • Saturday night and Monday night: designated UMAnitarian BOF opportunities – AI: Eve will send mail
    • Any possibility for remote participation in the Kantara workshop? – AI: Eve will ask Joni
  • SURFnet Kantara workshop ~Sep 4
    • Domenico may be able to attend, in addition to others we've heard about
  • August timeframe: 0.9 completion!
  • September: IDESG plenary, HL7, OIDC interop, MIT conference the week of Sep 16
    • IDESG: It will be in Tampa, colocated with a biometrics conference, ending on Sep 18 (mostly a travel day for people)
    • MIT: Sep 18 will involve a lot of discussion about Big Data etc.
    • MIT: Sep 19 is planned to be dedicated to OIDC and hopefully UMA interop – a save-the-date has been sent – there may be some healthcare profiling work done there
  • October has IIW, W3C, and a lot of other events
  • November may have Identity.next in the Netherlands
  • February 2015 (RSA conference): 1.0 completion!
  • March 2015 HIMSS: ONC pilot demo!

Discuss healthcare use cases

  • Surface some of the email discussion of recent weeks

Adrian has been advertising UMA as being able to solve all known human problems. (smile) Debbie works out of the HHS Office of the National Coordinator (ONC). There's been a push for RESTful solutions. OAuth, OIDC, and other related solutions have been talked about, and there's been some nascent UMA interest. She's gotten the okay to do a small pilot, and has reached out to the VA. The VA is very interested in data segmentation, privacy, data provenance, and consent. The notion of a RESTful approach to solving problems where XACML is already in the works is interesting. VA, Kaiser Permanente, ONC, and (Adrian's) Patient Privacy Rights (PPR?) effort are keen to do a live demonstration at HIMSS 2015. Profiling is of high importance, and it's also important to point to reference implementations. This has all led to the collaboration. The current outlook is a healthcare-related OIDC-enabled healthauth.org (question) pilot. The biggest concern is that ONC wants to know precisely how this will be done; they'll be looking at the profiling and reference implementation work.

Adrian notes that this is all preceded by a lot of "consent management" work; ONC has sponsored Justin's work over the summer at MIT. The big question is now is: How much of UMA is generic, and how much is sector-specific and needs to be profiled? And another question is: Who gets to choose the AS: the RO, or someone else in the ecosystem? Following on this, if it's not the RO's choice, what profile would be active?

Debbie adds: How do these systems need to scale? It's quite possible that a user could have many AS services, and then what? What's the needed infrastructure, and what are the needed trust frameworks?

Mike comments: UMA supports a number of different trust models. He'd like to focus less on the bindings and more on the core stuff. He's been working on the Juju app security project. This is a framework that defines OIDC, UMA, and SCIM used in concert by cloud apps. The goal is to drive down the cost of web security. UMA's core is already pretty complex, with three entities. But they definitely do need other agreements around them in deployment.

Eve observes that once we've pushed our three technical specs to "mature draft" specification status, it may be the perfect time to get the contractual/legal Binding Obligations spec to the same status. We do need to help third-party profilers to figure out what the right dividing line between "core" and "profile" is, and also to advise how third parties can create (profile) new access federations that enable horizontal (e.g. being listed in an app store) or vertical (e.g. healthcare) ecosystems – or both (an RLS is a health-related directory/registry of sorts). And it would be good to figure out the relationships between identity federations and access federations – where is there daylight and why? Where is it inappropriate to link them?

Mike is part of a group that has proposed an OAuth multi-party federation group (this is the one that Prateek from Oracle has been promoting). They're thinking of proposing this as an OAuth2 WG at IETF or at OASIS vs. at the OpenID Foundation, because it's important not just for, say, social login but also for B2B collaboration. This could involve things like standardizing scope descriptions; see the examples here.

Debbie points out that Direct Trust involves S/MIME etc. at a technical level, and FICAM involves technical details but at a fairly high level.

Adrian decries the state of healthcare interop based on its heavy profiling. He wants UMA to contain the sedimented wisdom about what's core and what's specific (maybe attributes, but try to minimize what goes here).

Let's agree to capture issues for every known third-party profile to consider whether it should be "first-party", and thence whether it should be included in interop activities.

AI: Eve: Create issues around the trust elevation profile and anticipated healthcare profiling, informed by Mike's federation example.

Editors' ad hoc meeting to edit specs into shape

  • Assuming at least Thomas and Maciej are available
  • Others can drop at this point if they like

Attendees

September event plans are noted below:

  • Eve (may try to do both XML Summer School and MIT)
  • Adrian (will try to attend Tampa and MIT events somehow)
  • Domenico
  • Thomas (will focus on MIT events)
  • Mike
  • Debbie (IDESG and MIT events)
  • Mark (SURFnet events)
  • Ann
  • Ryan (possibly IDESG)
  • Maciej

Ann is founder and CEO of World Knowledge, and is active in NSTIC and IDESG.

Next Meetings

  • Focus meeting Thu Jul 10 9-10am PT (time chart)
  • Focus meeting Thu Jul 17 9-10am PT (time chart)
  • All-hands meeting Thu Jul 24 9-10am PT (time chart)

Â