Wiki
Clone wikifapi / FAPI_Meeting_Notes_2018-05-09
FAPI WG Meeting Notes (2018-05-09)
Date & Time: 2018-05-09
Location: GoToMeeting https://global.gotomeeting.com/join/321819862
Agenda
The meeting was called to order at 14:08 UTC.
1. Roll Call
- Attending: Dave, Joseph, Ralph, Tom, Bjorn, Nat
- Guest:
- Regrets:
2. Adoption of the Agenda (Dave)
- An agenda was discussed and agreed verbally as none had been sent in advance.
3. Pull Requests
Those on the call accepted the change and recommended that it be merged in
There was agreement to go with Nat's proposed wording. Dave to update the pull request.
There was agreement to merge in the change. There was some discussion about the need to have a standards based approach to "lodging intent". OpenBanking, Stet and Berlin Group have all taken different approaches and none of them are using the request object endpoint. Dave to raise an issue for this.
Tom advised that we should hold on this - he will get back to us on the next call.
We discussed this pull request and then moved into a related issue, see below.
4. Issues
- https://bitbucket.org/openid/fapi/issues?status=new&status=open
- https://bitbucket.org/openid/fapi/issues/11/oauth-profile-should-mandate-rfc7636-pkce
We discussed this and came to the consensus that PKCE should be required for all clients in part 1, not just public clients. Joseph to create a pull request with this change.
This issue can be closed when the related pull request is merged
We discussed this issue and agreed to leave some comments on the issue. There was a discussion about whether the name needed to match up with FAPI at all.
Those on the call felt that the wording in FAPI was fine, even though it is more restrictive than the base standard.
We discussed this and agreed that Dave would try and raise the issue in the OAuth Working Group.
5. External Organizations
5.1. OpenBanking
Roll out is continuing. There was discussion about the conformance suite and the need for RPs to run it.
5.2. ISO/TC68/SC 9
Dave explained that redrafting is in process and that he will share more via the list.
6. AOB
6.1. Next Call
The next call is scheduled to be in the Pacific time zone.
- The meeting was adjourned at 14:50 UTC.
Updated