-
Notifications
You must be signed in to change notification settings - Fork 0
FAPI_Meeting_Notes_2023 11 02_Atlantic
Nat Sakimura edited this page Jul 10, 2026
·
1 revision
- Date & Time: 2023-11-02 14:00 UTC
- Location: https://zoom.us/j/97456084642?pwd=bTRFVzk4ZmlRK1M3bEprRlN5c3JFZz09
Agenda
The meeting was called to order at 14:03 UTC.
- Attendees: Domingos, Nat, Brian, Dima, Bjorn, Joseph, Victor, Kosuke, Chris
- Regrets: Mike L.
- AOB: Call will be cancelled next week due to IETF.
- AOB: 2024 Initiatives https://docs.google.com/presentation/d/1JYpgQJDR853CzGTlLU14qmE_i88t3zHt/edit#slide=id.p29
- We are cancelling the FAPI call as it collides with OAuth WG.
- Joseph and Nat are going to be there.
- About to publish standard. Sticking to the same security profile for now. FAPI1 Adv + PAR.
- There will be associated notes for people to get ready to FAPI2?
-
- PR 441
-
- https://bitbucket.org/openid/fapi/pull-requests/441
- We should not hide normative text in the NOTE. Dave to do another go.
-
- PR 444
-
- https://bitbucket.org/openid/fapi/pull-requests/444
- The typo needs to be fixed.
-
- PR 438 Phished code injection
-
- https://bitbucket.org/openid/fapi/pull-requests/438
- Passive form was removed from the PR. Nat approved.
- Joseph pointed out that something similar potentially need to be in FAPI2. Joseph will review the needs.
-
- PR 440 Clock Skew
-
- https://bitbucket.org/openid/fapi/pull-requests/440
- Mark to review the language.
-
- PR 442 improve wording around which grant and response types are supported
-
- https://bitbucket.org/openid/fapi/pull-requests/442
- We want to allow future specifications to be used with FAPI2 so we do not want to lock down only to response_type=code.
n/a
The UK and the US will go off daylight saving time next week and the week after, respectively. This meeting is hinged to UTC, so it means the meeting time will shift t for them. Please be aware of it.
- The call the week after conflicts with IETF OAuth WG F2F so we are cancelling it.
The meeting adjourned at 15:00.