3.1.   Open Banking (Chris)

• 120 attendees
• Video avaiable
• Takeaway: Good opportunity to push libraries authors to get through the certification.
• Implementers should use libraries if possible.
• Will send out survey for feedback later
• Will reach out to OIDC compliant implementers to test for FAPI certification
• EBA, FCA and other authorities don’t have any certification requirements yet
• Banks will not do it themselves without regulatory requirement or strong commercial benefit
• FCI and other regulators aren’t not very specific about which standards/certifications should be complied to.
• Seems to be too early phase for banks to be very specific technically
• Need to let EBA issue requirements instead of individual regulators
• Might take some security breaches before issuing requirements?
• EBA right now focused on customer experience complaints

3.2.   IIF (Nat)

• Drew attention to IIF and OIDF collaboration
• FAPI and eKYC WG will be establish collaboration here
• IIF membership largely of regulators, law makers, and policymakers

• Opportunity to point out merits of conformance, testing, and standards

3.3.   FDX/OIDF (Don)

You are not required to register for the workshop as a presenter but welcome to do so: https://www.eventbrite.com/e/openid-foundation-virtual-workshop-tickets-121075932373 This is a direct link to the virtual workshop session: https://global.gotomeeting.com/join/825700629

• Workshop will have keynote panel (Nat Sakimura, Don Cardinal, Anoop Saxena)
• Will talk about OIDF and FDX path going forward
• FDX acting like SRO (Self Regulatory Org)
• FDX announcing unofficial support of FAPI and collaboration of FAPI 2.0
• 3 areas of engagement
  1. Concurrent outreach/collaboration like Global Summit
  2. Concurrent technical collaboration
  3. FDX Increasing Conformance to OIDC and FAPI
     • Will drive demand for certification services

4.1.   Mexico (Chris)

• Documents show support for implicit flow.
• Chris to try to find definitive source documents for requirements.
• Timeline is uncertain.

4.2.   ETSI (Torsten/Dave)

• Dave sent a draft response to FAPI mailing list regarding OBE/PRETA JWS HTTP Signing Profile for feedback. Will need to finalize it within the next few days.
• Profile uses JWS 7797 without base64 encoding payload
• May want to propose creating a more generic FAPI which they could profile into depending on their response.
• PRETA is attempting a commercial Open Banking directory for Europe. Seems like a enterprise version of OBIE. Supports literal interpretation os PSD2.
• None of the standards bodies have agreed to implement the draft spec yet.

4.3.   Australia (Dima/Stuart)

• Had another Data Recipient accreditation (total 3 now).
• A version of the Rules consultation circulated focusing on different types of accredited entities (complex scenarios).
• Last week, "conformance test suite" was presented to the industry.
• Incomplete set of tests but it is not designed to be comprehensive.
• It's designed for regulators to do the final check instead of assisting participants with accreditation. It’s trying to replace industry testing environment (coordinated sandbox used for July release).
• There are no mandates for Banks to support sandboxes.
• Industry testing environment ironed out a lot of issues due to data recipients and data holders connecting to each other.
• It’s essentially payload testing of some APIs not like FAPI testing different scenarios. Mainly focused on CDS specification. Not testing normative specifications.

4.4.   Berlin Group (Francis)

• n/a till mid of November.

4.5.   European Commission (Mark/Torsten)

• n/a

4.6.   UK (Ralph)

5.1.   FAPI 1.0 Last Call (Nat)

• Closes today
• Public review period will be for 6 weeks
• See Issues
• Revisiting question regarding changing FAPI 1.0 to Baseline and Advanced

• Still possible to provide feedback
• Changing from R/RW will affect introductory text
• Also implementations already exist and refers to R/RW
• Another suggestion was to call it Part ½
• Nat will solicit feedback from group regarding name, will also create issue ticket

5.2.   FAPI 2.0 Baseline (Daniel)

• Need to bring in more reviewers.

5.3.   FAPI 2.0 Advanced (Daniel)

• Main sticking point is signatures. #309.
• ETSI and OBIE discussion is relevant.

5.4.   Grant Management (Torsten/Stuart)

6.1.   #322 Editorial: Section 5.2.2.2.1. Duplicate Clause? (Ralph)

• https://bitbucket.org/openid/fapi/issues/322/editorial-section-52221-duplicate-clause

A lengthy discussion on how to test. The discussion to be continued.