Skip to content

FAPI_Meeting_Notes_2025 02 20_Pacific

Jump to bottom
Nat Sakimura edited this page Jul 10, 2026 · 1 revision

1.   FAPI WG Agenda & Meeting Notes (2025-02-20)

Date & Time: 2025-02-21 00:00 UTC Location: https://zoom.us/j/97456084642?pwd=bTRFVzk4ZmlRK1M3bEprRlN5c3JFZz09

The meeting was called to order at 00:00 UTC.

2.   Roll Call (Anoop)

  • Attendees: Nat, Dima, Anoop
  • Regrets:

3.   Events Update

  • OAuth Security Workshop 2025 (February 26-28, 2025) Location: Reykjavik, Iceland
  • OIDF is a sponsor
    • Final deadline for presentation submissions: January 12, 2025
    • Certification team will meet prior to workshop
  • DICE: March 4-5 in Zurich
  • ISO/IEC JTC 1/SC 27/WG5: March 10-15, 2025 in Fairfax
  • ISO/IEC JTC 1/SC 27: March 17-18, 2025 in Fairfax
  • MOSIP Connect: March 11-13 in Philippines
  • IETF: March 15-21 in Bangkok
  • OIDF Workshop: April 7th (prior to IIW)
  • IIW Spring 2025: April 8-10
  • FDX (US) Summit April 21-24 (Washington/Gaylord National Harbor, US)

3.1.   OIDF calendar

OIDF calendar on website is current: https://openid.net/calendar/

4.   Liaison/Ext Org

  • US open banking CFBB approves FDX (Financial Data Exchange) as standard body.

https://www.consumerfinance.gov/about-us/newsroom/cfpb-approves-application-from-financial-data-exchange-to-issue-standards-for-open-banking/

5.   FAPI 2.0 Security profile and attacker model is FINAL

FAPI 2 Security specifications approved
  • The results announcement and updated final spec links (prepared by Dave Tonge) were being finalized for publication later that day.
  • A follow-up would be sent via the working group mailing list once published.

6.   Issues

  • [Issue #724] Move FAPI 1/ FAPI 2 comparison table from Spec
    • Dima raised the issue that the comparison table might not be relevant for ecosystems adopting FAPI 2 directly
    • Determined it's too late to remove as specs are already approved
    • Issue closed
  • Issue #722: Summary of changes between FAPI2-SP-ID2 and final**
    • Dima is working on documenting differences between the last implementer's draft and the final version
    • Requested reviewers to help validate the document
    • Particularly relevant for ecosystems migrating from ID2 to the final version
  • Issue #598: State parameter length**
    • Discussion about what happened to the state parameter length requirements
    • General recollection that it was moved to implementation guidelines
    • Current spec only mentions state parameter value could exceed 1,000 characters
  • Issue #425: FAPI 2.0 purpose and FAPI WG scope**
    • Nat and Dave have been exchanging emails to move this forward
  • Other issues:
    • Conformance team will discuss the private key JWT audience issue at their in-person meeting next week

7.   Next Call

Next call will be an Pacific Call. Next Pacific call will be in Next year (03-06-2025 @ 5pm PST) UTC - 03-07-2025 1:00 AM.

Clone this wiki locally