FAPI_Meeting_Notes_2019 06 12_Atlantic

FAPI WG Meeting Notes (2019-06-12)

Date & Time: 2019-06-12 14:00 UTC

Location: GoToMeeting https://global.gotomeeting.com/join/321819862

Agenda

• 1.   Roll Call
• 2.   Adoption of the Agenda (Nat)
• 3.   Pull Requests
• 4.   Issues
  • 4.1.   Follow-ups of last week's items
  • 4.2.   #212: FAPI-CIBA; should id_token tie itself to the auth request?
• 5.   AOB
  • 5.1.   Next Call

The meeting was called to order at 14:__ UTC.

1.   Roll Call

• Attending:

  • Bjorn, Chris, Joseph, Kosuke, Nat, Dave

• Regrets:

2.   Adoption of the Agenda (Nat)

3.   Pull Requests

• https://bitbucket.org/openid/fapi/pull-requests/106/first-attempt-at-removing-public-client/diff
• https://bitbucket.org/openid/fapi/pull-requests/107/pushed-request-uri/diff
• https://bitbucket.org/openid/fapi/pull-requests/108/fixed-183/diff
• https://bitbucket.org/openid/fapi/pull-requests/93/fixing-typos/diff

4.   Issues

4.1.   Follow-ups of last week's items

• #223 Need of a customer unique/immutable identity as part of ID Token (Nat)
• #219 JARM: expires_in should be a number (Brian)
• #218 LoA3 requirement in part2 may be too much (Joseph)
• https://github.com/openid/fapi/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22component%3A%20CIBA%22

4.2.   #212: FAPI-CIBA; should id_token tie itself to the auth request?

To be treated For I-D 2

A question was posed by Torsten, which took most of the call.

5.   AOB

5.1.   Next Call

• Atlantic "Spec" call next week.

The meeting was adjourned at 14:__ UTC.