[Openid-specs-fapi] Re figo API (was Re: AW: (Correction) Friendly reminder and agenda for Sept. 14 Call)
nat at sakimura.org
Wed Sep 14 12:53:22 UTC 2016
That would be good. Maybe in two weeks time as it would be easier for
On 2016-09-14 20:55, Anton.Taborszky at telekom.de wrote:
> Hi Nat,
> thank you for your feedback. I don't think that we should put the FIGO
> API on today's agenda as it is of short notice for everyone. What
> about the following call?
> Best Anton
> -----Ursprüngliche Nachricht-----
> Von: Nat Sakimura [mailto:nat at sakimura.org]
> Gesendet: Mittwoch, 14. September 2016 13:27
> An: Taborszky, Anton
> Cc: openid-specs-fapi at lists.openid.net
> Betreff: Re figo API (was Re: AW: [Openid-specs-fapi] (Correction)
> Friendly reminder and agenda for Sept. 14 Call)
> Hi Anton,
> Yes, with my cursory look, it is pretty close in some sense -- though
> they need to lock down the OAuth security more, besides they are
> mixing up OAuth 2 Authorization with Authentication to start with.
> What I have written in the WD1 clause 5 and 6 is pretty much the
> minimum requirement when the client wants to support multiple
> authorization servers. I cannot see them in the figo documentation.
> Assumption might be that they are the aggregator and the clients only
> talks to them. Even then, depending on the environment that the client
> is in, using RFC7636 etc.
> would be advisable.
> Also, DDA apparently is much richer and complete in the supported
> products sense.
> With figo API, I am not sure how to support futures, options, etc.
> Also, I cannot readily see how to express tax efficient investment
> plans but it may be hiding behind.
> Another shortcoming that I see in figo is that they do not seem to
> have Open Data for Banks, e.g., ATM location, products information,
> etc. We need them as per required by the UK Open Banking Standard.
> But then, I have just looked at if for couple of minutes. I need more
> time to study them.
> Thanks for the info. Would you like to add this to today's agenda?
> On 2016-09-14 19:41, Anton.Taborszky at telekom.de wrote:
>> Last week, I came across the following website: http://figo.io (only
>> german). However, the api documentation is in english:
>> Isn't that mainly the goal of the FAPI working group?
>> Talk to you shortly
>> -----Ursprüngliche Nachricht-----
>> Von: Openid-specs-fapi
>> [mailto:openid-specs-fapi-bounces at lists.openid.net] Im Auftrag von Nat
>> Sakimura via Openid-specs-fapi
>> Gesendet: Mittwoch, 14. September 2016 11:59
>> An: Openid-specs Fapi
>> Betreff: [Openid-specs-fapi] (Correction) Friendly reminder and agenda
>> for Sept. 14 Call
>> Previously, I sent out the notice with wrong date.
>> The time that I have sent was already past the time so I suppose it
>> was obvious, but I would like to apologize for the confusion.
>> The calendar is showing the correct date anyways.
>> Please always refer to the group calendar at
>> This is the master information.
>> Dear FAPI Members:
>> Here is a friendly reminder and the agenda for the Sept. 14 Call.
>> Looking forward to talk with you.
>> Nat Sakimura
>> FAPI WG Meeting Notes (2016-09-14)
>> Date & Time: 2016-09-14 14:00 UTC
>> (07:00 PDT, 15:00 UK, 16:00 Denmark, 23:00 JST)
>> Location: GoToMeeting https://global.gotomeeting.com/join/321819862
>> 1. Roll Call
>> 2. Adoption of the Agenda
>> 3. External Org Relationships
>> 3.1. UK Implementation Entity (Dave)
>> 3.2. Federal Reserve of Minnesota (John)
>> 3.3. ECB Consultation (Dave)
>> 3.4. X9 (Paul?)
>> 4. Branch issue/26 Error messages (Sascha)
>> 5. Working Draft 01
>> 5.1. Review Results (John, Brian)
>> 6. Issues
>> 6.1. #7 Open Data (Dave)
>> 6.2. #16 Client Authentication -- Do we need TLS mutual
>> authentication? (Nat)
>> 6.3. #28 International names for retirement savings account names
>> 7. Events
>> 7.1. Pre-IIW (John)
>> 7.2. Pre-IETF (Nat)
>> 8. AOB
>> Openid-specs-fapi mailing list
>> Openid-specs-fapi at lists.openid.net
More information about the Openid-specs-fapi