-
Notifications
You must be signed in to change notification settings - Fork 0
FAPI_Meeting_Notes_2024 04 04_Pacific
Date & Time: 2024-04-05 00:00 UTC Location: https://zoom.us/j/97456084642?pwd=bTRFVzk4ZmlRK1M3bEprRlN5c3JFZz09
Agenda
The meeting was called to order at 00:00 UTC.
- Attendees: Mark, Dima, Anoop, Ralph
- Regrets: Nat
Rome April 10-12 – final call for speakers is open until March 10th.
All details here: https://oauth.secworkshop.events/osw2024
on Monday, April 15th in Sunnyvale – registration now open and required: https://openid.net/registration-oidf-workshop-monday-april-15-2024/
WG is hosting a hybrid meeting on Friday, April 19, 2024 after IIW Spring 2024. The meeting will allow for in-person and virtual participation and will be hosted at Google in Sunnyvale, CA (address and meeting room to be confirmed). Note that registration is only required if you are attending in-person:
Please register if you are planning to participate in-person so we can plan accordingly.
May 28-31, Las Vegas
OIDF has a meeting room available for use for the duration of the event
Any working groups wanting to hold a F2F meeting should contact Mike Lescz to coordinate.
https://bitbucket.org/openid/fapi/pull-requests/475 (Approved)
https://github.com/openid/fapi/issues/662
Remove normative text regarding state length
Add note that state is not used for CSRF but may be used by clients for application state. State may be JWTs which may be large.
New PR will be created. (remove prescription).
Some ecosystems use CIBA to implement proprietary authorization APIs There is a new parameter required to initiate the CIBA flow. The authorization server needs to pass an parameter to the client application.
More discussion needed
The issue is description change from FAPI 1.0 and FAPI 2.0 Mark will update comment on the ticket
https://github.com/openid/fapi/issues/673
Next call will be an Pacific Call. Next Pacific call will be in two weeks (04-18-2024 @ 5pm PST) UTC - 04-19-2024 1:00 AM.