-
Notifications
You must be signed in to change notification settings - Fork 0
FAPI_Meeting_Notes_2024 03 21_Pacific
Date & Time: 2024-03-22 00:00 UTC Location: https://zoom.us/j/97456084642?pwd=bTRFVzk4ZmlRK1M3bEprRlN5c3JFZz09
Agenda
The meeting was called to order at 00:00 UTC.
- Attendees: Dima, Michael, Mark, Brian, Adam Bradley, Ralph, Anoop
- Regrets:
IETF 119 coming up on Mar 16 - 22. Brisbane
https://datatracker.ietf.org/meeting/119/agenda
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.
4.1. Issue #670 Clarify allowed use of state and required CSRF protection in FAPI 2.0 SP
https://github.com/openid/fapi/issues/670
Text is to be created.
Proposed “The PKCE challenge shall be transaction-specific and securely bound to the client and the user agent in which the transaction was started.” From BCP 2.1.1 Proposed changing “transaction” to “flow” “Transaction” needs to be defined if used
https://github.com/openid/fapi/issues/671
Need more broader discussion. Not closed on 224 for EC.
https://github.com/openid/fapi/issues/658 https://bitbucket.org/openid/fapi/pull-requests/475
Next call will be an Pacific Call. Next Pacific call will be in two weeks (04-04-2024 @ 5pm PST) UTC - 04-05-2024 1:00 AM.