[Openid-specs-ab] OpenID AB/Connect Call Note (2019-12-09)

Nat Sakimura sakimura at gmail.com
Tue Dec 10 00:01:42 UTC 2019


OpenID AB/Connect Call Note (2019-12-09)

Date: 2019-12-09 15:05 UTC

Location: GoToMeeting https://www3.gotomeeting.com/join/695548174

Agenda

   - 1.   Roll Call
   <https://bitbucket.org/openid/connect/wiki/Connect_Meeting_Notes_2019-12-09_Atlantic#rst-header-roll-call>
   - 2.   Creation of the agenda
   <https://bitbucket.org/openid/connect/wiki/Connect_Meeting_Notes_2019-12-09_Atlantic#rst-header-creation-of-the-agenda>
   - 3.   AppAuth Process (George)
   <https://bitbucket.org/openid/connect/wiki/Connect_Meeting_Notes_2019-12-09_Atlantic#rst-header-appauth-process-george>
   - 4.   Healthcare Use Case (Tom)
   <https://bitbucket.org/openid/connect/wiki/Connect_Meeting_Notes_2019-12-09_Atlantic#rst-header-healthcare-use-case-tom>
   - 5.   AOB
   <https://bitbucket.org/openid/connect/wiki/Connect_Meeting_Notes_2019-12-09_Atlantic#rst-header-aob>

The meeting was called to order at 15:08 UTC.
1.   Roll Call
<https://bitbucket.org/openid/connect/wiki/Connect_Meeting_Notes_2019-12-09_Atlantic#rst-header-id1>

   - Present: Nat, Edmund, George, Tom
   - Regret: Mike

2.   Creation of the agenda
<https://bitbucket.org/openid/connect/wiki/Connect_Meeting_Notes_2019-12-09_Atlantic#rst-header-id2>

   - As no proposed agenda was previously sent out, it was created on the
   spot.

3.   AppAuth Process (George)
<https://bitbucket.org/openid/connect/wiki/Connect_Meeting_Notes_2019-12-09_Atlantic#rst-header-id3>

AppAuth for Android has been hanging out for more than a year iOS version
is still maintained by William. Android version was maintained by Ian.
Verizon Media is willing to take over but the process is not clear.

   - https://openid.net/specs/openid-connect-registration-1_0.html

It is supposed to be wide open.

Issue https://github.com/openid/AppAuth-Android/issues/444 calls for new
maintainer of the Android version. George stated that there are Verizon
Media developers who would like to be. Nat suggested them to chime into the
ticket.

ACTION: Verizon Media Team to volunteer in the issue.

Also, the point that there is no process defined was raised. The closest to
that OpenID Foundation has is probably the certification.

ACTION: Nat to contact the certification team to get the document.

Once the document was obtained, the WG should look at it and make necessary
changes and convene a call with new and old maintainers. Perhaps we will
need a scheduled dev-team call as well, though it may fall out of WG's
formal activity.
4.   Healthcare Use Case (Tom)
<https://bitbucket.org/openid/connect/wiki/Connect_Meeting_Notes_2019-12-09_Atlantic#rst-header-id4>

Tom asked a question around the healthcare device App that he is writing.
The initial question was whether the AppAuth supports dynamic client
registration. George's answer was "probably does not."

Tom's use case was the EHR/PHR registering to a Self-issued OP where the
client (EHR/PHR) has a software statement.

George suggested looking at the software statement in section 2.3 of
RFC5791.

   - https://tools.ietf.org/html/rfc7591#section-2.3 is the software
   statement.

Tom replied that he will have a look and also mentioned of Identity
statement in Federation Doc.
5.   AOB
<https://bitbucket.org/openid/connect/wiki/Connect_Meeting_Notes_2019-12-09_Atlantic#rst-header-id5>

The call closed at 15:45 UTC

-- 
Nat Sakimura (=nat)
Chairman, OpenID Foundation
http://nat.sakimura.org/
@_nat_en
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20191210/bfd710ea/attachment.html>


More information about the Openid-specs-ab mailing list