Skip to content

FAPI_Meeting_Notes_2026 04 08_Atlantic

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

FAPI Working Group Atlantic Call — Meeting Notes

Date: Wednesday, April 8, 2026 Time: 14:00 UTC Chair: Nat Sakimura Note-taker: (from transcript)


Attendees

Name Organization
Nat Sakimura nat.consulting (Chair)
Hideki Ikeda (not specified)
Mike Leszcz OpenID Foundation
Dima Postnikov (Co-chair)
Imran Ulghar Open Banking Limited (OBL)
Kosuke Koiwai (not specified)
George Fletcher (not specified)
Craig Borysowich IMedge (CA)
Filip Skokan (not specified)
  • Apologies: Dave Tonge (Co-Chair)

0. Note Well

Mike Leszcz presented the OpenID Foundation Note Well, covering:

  • The OIDF Code of Conduct Policy
  • The OIDF Antitrust Policy
  • Requirement for a signed Contribution Agreement to participate in OIDF Working Groups
  • Requirement for a signed Participation Agreement to participate in OIDF Community Groups
  • All reference policies are available at https://openid.net/policies

1. Roll Call

Roll call conducted by chat. Attendees listed above.


2. Adoption of Agenda

The following agenda was adopted without objection:

0.  Note Well
1.  Roll Call (Dave/Nat)
2.  Adoption of Agenda (Nat)
3.  Events (Mike L.)
4.  External Orgs & Liaisons (Mike L.)
5.  Publication Issues (Nat)
6.  PRs (Nat)
7.  Issues (Nat)
8.  AOB (Nat)

3. Events

Mike Leszcz presented the updated events calendar. The following events were noted:

Date Event Location
April 14, 2026 OECD Working Party on Digital Security Paris
April 22–23, 2026 IAM Tech Day São Paulo
April 27, 2026 OIDF Workshop prior to IIW Spring 2026 (registration required) Mountain View
April 28–30, 2026 IIW Spring 2026 Mountain View
May 12–15, 2026 ID4Africa Abidjan
May 19–22, 2026 EIC 2026 Berlin
May 27–29, 2026 OAuth Security Workshop (OSW) Leipzig, Germany
June 2, 2026 FIDO Authenticate APAC 2026 Singapore
June 9–10, 2026 IDENTITY WEEK (newly added) Amsterdam
June 15–18, 2026 Identiverse Las Vegas
June 22–24, 2026 Dice 2026 Copenhagen
July 18–24, 2026 IETF 126 Vienna
August 26, 2026 OIDF-J OpenID Summit 2026 Special Edition (newly added) Tokyo
September 1–3, 2026 Global Digital Collaboration Conference 2026 Geneva
September 14–17, 2026 ISO/IEC JTC1/SC 17 Plenary Chengdu, China
October 19–21, 2026 FIDO Authenticate 2026 Carlsbad, CA
November 2, 2026 OIDF Workshop prior to IIW Fall 2026 Mountain View
November 3–5, 2026 IIW Fall 2026 Mountain View
November 14–20, 2026 IETF 127 San Francisco
December 7–9, 2026 Gartner IAM US Las Vegas

Highlights:

  • OIDF Workshop (April 27): Registration is required for both in-person and virtual attendance. Registration link: https://openid.net/registration-open-for-openid-foundation-hybrid-workshop-on-mon-27th-april-2026/
  • OIDF-J OpenID Summit 2026 Special Edition (August 26, Tokyo): A new event added this call. Mike noted that OIDF Japan hosts a major summit every four years (next planned for 2028); this is a smaller bridge event in advance of that.
  • IDENTITY WEEK Amsterdam (June 9–10): Nat reported this event from the eKYC-IDA Working Group. Mike will add it to the calendar.

To submit additional 2026 events for the calendar, contact mike.leszcz@oidf.org.


4. External Orgs & Liaisons / Ecosystem Engagement

Mike Leszcz provided the following ecosystem updates:

  • Chile (CMF): Regulation expected in place by August 2026. A few FAPI 2 certifications anticipated in 2026 as a "pilot," with the ecosystem going live in earnest in early 2027. CMF confirmed Shared Signals adoption will happen at a later stage. Domingos Creado now has access to the mock bank and CMF directory to support test development. CMF and Minsait will identify three ecosystem partners to assist with test validation. Directed funding for test development is in process.
  • Peru: OIDF (Mike Leszcz and Domingos Creado) confirmed participation in an ecosystem outreach webinar in late May. The session will introduce OIDF, present OpenID specifications used in open data ecosystems, highlight the importance of conformance testing and self-certification, and discuss global spec adoption. Dates to be confirmed and shared in a future update.
  • Saudi Arabia (SAMA): Directed funding for a new KSA FAPI 2 Profile has been received. Domingos Creado has commenced development of the KSA FAPI 2 Profile. Ecosystem participants will certify to the new profile once it is in production.

Member Reminders (from chat):

Discussion — iGov Profile:

Dima Postnikov asked about the nature of the updates in the new iGov Implementer's Draft, given it could be indirectly relevant to FAPI. Nat Sakimura, who had been reading the draft before the call, noted:

  • The draft includes post-quantum guidance, with a NIST reference to ECDH-AML Chem.
  • TLS algorithm suites are explicitly specified (rather than by reference to BCP-195 or the IANA registry).
  • TLS 1.3 appears to be required.
  • These aspects put iGov slightly ahead of FAPI in terms of cryptographic specificity.

Dima noted this could be relevant to borrow from in the future. Nat encouraged participants to read the draft and form their own views. The relevant guidance is in Section 1.4 of the specification.

Mike Leszcz departed the call after completing his updates.


5. Publication Issues

Nat Sakimura reported a publication issue with the FAPI 1 Part 2 Errata 1 Draft:

  • The FAPI 1 Part 1 errata draft was successfully pushed the previous Thursday.
  • When Nat attempted to push the FAPI 1 Part 2 Errata 1 draft late Friday (his local time), the publication suite had changed its check logic, resulting in a push failure.
  • Nat is currently blocked from pushing and is working to resolve this.
  • Publication process is now insisting on adding an Abstract to FAPI 1 Part 2 (which is absent from the published final version, and needs to be removed from ISO submission); Nat is pushing back on this addition.

6. Pull Requests

PR #563 — BCP-195 Reference Correction

  • Link: https://bitbucket.org/openid/fapi/pull-requests/563/diff
  • Nat reported that in a prior version of this PR, the reference to BCP-195 was not formatted correctly. This has now been corrected.
  • Content is otherwise unchanged from last week.
  • Decision: Nat will merge the PR after the call once he has written the commit message.

7. Issues

Issue #738 — Deprecation of FAPI 2 ID2 Tests

  • Link: https://github.com/openid/fapi/issues/738
  • The group had been waiting for Dima Postnikov to return with a status from ConnectID.
  • Dima's update: Now that he is no longer at ConnectID, he will nudge them directly. The practical effect is that no new certifications to the FAPI 2 Implementer's Draft will be possible once tests are decommissioned; existing published certifications on the website will be preserved. New certifications are already flowing through for the Final specification.
  • There remain some older certifications (e.g., ConnectID, UAE) that have not yet been recertified to the Final. Joseph Heenan has been pinged on the ticket regarding the UAE side.
  • Status: Dima will comment on the issue when he has more information. To be revisited next week.

Issue #583 — Using OpenID Federation and FAPI Together

  • Link: https://github.com/openid/fapi/issues/583
  • The issue was originally created by Joseph Heenan; the most recent comment was from Dima Postnikov in January, indicating plans to create a profile of OpenID Federation for open data ecosystems.
  • Discussion: Dima indicated this is not a top priority currently but may still be relevant to work in the Ecosystems Community Group. He will check with Joseph to understand the original query better.
  • Action: Nat assigned the issue to Dima Postnikov.

Issue #839 — FAPI 2.0 OSCAL Profile

  • Link: https://github.com/openid/fapi/issues/839
  • The primary contributor is not present on this call (Dave Tonge absent). Nat will ping the relevant party to ask if they can return to this issue.
  • Status: Deferred; Nat to follow up.

Issue #835 — 5.2 Network Layer Protections

Issue #420 — Multi-Party Consents

  • Link: https://github.com/openid/fapi/issues/420
  • Nat noted that substantive discussion on this issue dates back to April 2022 — nearly four years ago.
  • Assigned to Dima Postnikov. Dima acknowledged needing to review all his assigned issues; there may have been recent relevant work in this space.
  • Action: Dima to review and report back when convenient (next week or the week after).

Issue #290 — x-fapi-interaction-id Across Client-to-AS and RS Interactions

  • Link: https://github.com/openid/fapi/issues/290
  • Also assigned to Dima. Dima confirmed that this likely belongs in the FAPI Implementation Advice document.
  • Action: Dima to review along with other assigned issues and report back.

General note: Nat shared the full list of issues assigned to Dima (link: https://github.com/openid/fapi/issues?q=is%3Aissue%20state%3Aopen%20assignee%3Adpostnikov) and asked him to work through them — particularly those unrelated to grant management — and return with updates.

Filip Skokan noted he holds an "honorary" position on the certification team and is not actively up to date on certification-related matters, though he acknowledged having opinions on the open issues.


8. Any Other Business

No other business was raised.

Nat thanked participants and closed the call.


Action Items

# Action Owner Due
1 Merge PR #563 (write commit message and merge after call) Nat Sakimura Immediately post-call
2 Nudge ConnectID regarding FAPI 2 ID2 recertification; comment on Issue #738 Dima Postnikov Before next call
3 Ping Joseph Heenan re: UAE side of Issue #738 Nat Sakimura (done during call)
4 Review Issue #583 with Joseph Heenan; assess OpenID Federation profile work Dima Postnikov When convenient
5 Ping relevant contributor to ask if they can return to Issue #839 (OSCAL Profile) Nat Sakimura ASAP
6 Review all issues assigned to Dima (excluding grant management) and report back Dima Postnikov Next 1–2 calls
7 Add IDENTITY WEEK Amsterdam (June 9–10) to the OIDF events calendar Mike Leszcz Post-call
8 Resolve Bitbucket push issue for FAPI 1 Part 2 Errata 1 Draft Nat Sakimura ASAP

Reference Links

Description URL
PR #563 — BCP-195 Reference Correction https://bitbucket.org/openid/fapi/pull-requests/563/diff
Issue #738 — Deprecation of FAPI 2 ID2 Tests https://github.com/openid/fapi/issues/738
Issue #583 — Using OpenID Federation and FAPI Together https://github.com/openid/fapi/issues/583
Issue #839 — FAPI 2.0 OSCAL Profile https://github.com/openid/fapi/issues/839
Issue #835 — 5.2 Network Layer Protections https://github.com/openid/fapi/issues/835
Issue #420 — Multi-Party Consents https://github.com/openid/fapi/issues/420
Issue #290 — x-fapi-interaction-id Across Client-to-AS and RS https://github.com/openid/fapi/issues/290
Issues assigned to Dima Postnikov https://github.com/openid/fapi/issues?q=is%3Aissue%20state%3Aopen%20assignee%3Adpostnikov
OIDF Workshop April 27 — Registration https://openid.net/registration-open-for-openid-foundation-hybrid-workshop-on-mon-27th-april-2026/
iGov Implementer's Draft Vote https://openid.net/notice-of-vote-to-approve-proposed-implementers-draft-of-international-government-assurance-profile-for-oauth-2/
iGov Member Poll (direct link) https://openid.net/foundation/members/polls/403
OpenID Federation 1.1 Final — Public Review https://openid.net/public-review-period-for-proposed-openid-federation-1-1-final-specifications/
OpenID Connect ASC 1.0 — Public Review https://openid.net/public-review-period-for-proposed-implementers-draft-of-openid-connect-advanced-syntax-for-claims-1-0/
OIDF Policies https://openid.net/policies

Next Meeting

FAPI WG Atlantic Call Wednesday, April 15, 2026 — 14:00 UTC

Clone this wiki locally