FAPI_Meeting_Notes_2018 03 06

FAPI WG Meeting Notes (2018-03-06)

Date & Time: 2018-03-06 23:00 UTC

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

Agenda

• 1.   Roll Call
• 2.   Adoption of the Agenda (Nat)
• 3.   External Organizations
  • 3.1.   FS-ISAC (Anoop/Paul)
  • 3.2.   ISO/TC 68/SC 9 (Dave)
• 4.   Pull Requests
• 5.   Issues
• 6.   Events
  • 6.1.   OAuth Security Workshop
  • 6.2.   Open Banking Workshop
  • 6.3.   IETF 101 London
• 7.   AOB
  • 7.1.   Next Call
  • 7.2.   Memo

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

1.   Roll Call

• Attending: Nat, Dave, Joseph, Tom, Edmund, John, Bjorn, Tony

  • Guest: Anoop

• Regrets:

2.   Adoption of the Agenda (Nat)

3.   External Organizations

3.1.   FS-ISAC (Anoop/Paul)

3.2.   ISO/TC 68/SC 9 (Dave)

4.   Pull Requests

• None

5.   Issues

• https://github.com/openid/fapi/issues?q=is%3Aissue%20state%3Aopen
• #135 https://github.com/openid/fapi/issues/135
• #137 https://github.com/openid/fapi/issues/137

6.   Events

6.1.   OAuth Security Workshop

• 14, 15, 16 March @ Trento

6.2.   Open Banking Workshop

• Morning 21 March, Microsoft
• Any work around the ux of redirect model and decoupled, and how to align with Europe.

6.3.   IETF 101 London

• 18 - 23 March
• Reciprocal OAuth (was Mutual OAuth draft before) may be interesting for Open Banking.

7.   AOB

7.1.   Next Call

The next call is scheduled to be in the Pacific time zone.

• The meeting was adjourned at 23:__ UTC.

7.2.   Memo

There are two main use cases for this standard:

A Financial Institution or Service Provider uses the standard for it’s own applications and services. A Financial Institution or Service Provider uses the standard to expose an API for third party applications and services to use. The second use case will allow the market to transition from the current practice of “screen scraping”, which is brittle and insecure, to a robust API with structured data and a strong security model.