-
Notifications
You must be signed in to change notification settings - Fork 0
FAPI_Meeting_Notes_2025 01 15_Atlantic
Nat Sakimura edited this page Jul 10, 2026
·
1 revision
- Dave Tonge (Chair)
- Mike Leszcz (OIDF)
- Joseph Heenan (OIDF & Authlete)
- Filip Skokan
- Brian Campbell
- Bjorn Hjelm
- Hideki Ikeda
- Kosuke Koiwai
- Peter Wallach (Mastercard)
- Chris Wood
- Robert Gallagher (Mastercard)
- Peter Stanley (OBL)
- Domingos Creado
- Imran Ulghar (OBL)
- Roll Call
- Adoption of Agenda
- Events
- External Orgs & Liaisons
- PRs
- Issues
- AOB
- OSW 2025: Feb 26-28 in Reykjavik, Iceland
- 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
- Brazil (Open Finance & Insurance): Annual FAPI recertification cycle has started
- Expected to continue through Q1 into April
- United Arab Emirates:
- RP certifications are open with several entities already certified
- OP certification test recently completed by Domingos, to be pushed to production soon
- Vote announcement: Saturday, January 25, 2025
- Early voting opens: Saturday, February 1, 2025
- Voting period: February 8-15, 2025 (7 days)
- Discussion on approach for different specs:
- For FAPI 1 errata: Decision to wait for underlying specs to be updated
- For FAPI CIBA: Agreement that it falls back to core FAPI specifications
- For CIBA itself: Recommendation to wait for OIDC errata rather than making piecemeal changes
- Action: Dave to add comments to both PRs explaining the decision
- Issue #716 discussed regarding reliance on draft OAuth 2.0 JWT Introspection Response
- Brian confirmed the draft is progressing toward publication
- Agreement to:
- Proceed with the working last call process
- Add a note in the document about the draft reference to be updated before final publication
- Update references once RFC is published
Discussion of three main areas to focus on:
- FAPI CIBA
- HTTP Signatures
- Implementation & Deployment Advice
Decision: Prioritize FAPI CIBA due to:
- Existing conformance tests
- Potential deployment plans in Brazil
- Relatively contained scope of remaining work
Additional topics discussed:
- Grant Management
- Client Registration options
- Federation with FAPI 2
- Need to analyze compatibility
- Questions about interoperability profiles
- Known implementations by:
- Authlete
- Connect2id
- Radium (in progress)
Action: Gather input from implementers on Federation+FAPI 2 compatibility before considering any specification work.
- Dave to prepare CIBA issues for review next week
- Dave to follow up on collecting Federation implementation feedback
- Working group to proceed with Message Signing working last call
Next call scheduled for regular time next week.