[Openid-specs-fapi] Issue #140: New name for FAPI (openid/fapi)

Vladimir Dzhuvinov vladimir at connect2id.com
Fri May 11 09:20:46 UTC 2018


Good point! There must still be a way to keep the "plus" though :)


On 11/05/18 11:07, Dave Tonge wrote:
> While I quite like OpenID Plus, part 1 of FAPI doesn't require OpenID
> Connect, i.e. for confidential clients there is no requirement for the
> openid scope and for id tokens to be issued.
> The spec draws on some of the clauses in OIDC, but isn't an OIDC profile -
> rather its an OAuth 2 profile.
>
> The downside with OIDC as well is that a lot of people still associate it
> only with identity, despite the fact that many of the clauses in the OIDC
> spec are unrelated to identity.
>
>
> On 11 May 2018 at 08:55, Vladimir Dzhuvinov via Openid-specs-fapi <
> openid-specs-fapi at lists.openid.net> wrote:
>
>> +1 for OpenID Plus :)
>>
>>
>> On 11/05/18 02:14, Chris Michael via Openid-specs-fapi wrote:
>>> Open ID Plus is better IMO
>>>
>>>
>>> Chris Michael
>>> Head of Technology
>>> Open Banking
>>> +44 7767 372277
>>> http://www.openbanking.org.uk
>>>
>>> ________________________________________
>>> From: Openid-specs-fapi <openid-specs-fapi-bounces at lists.openid.net> on
>> behalf of Mike Schwartz via Openid-specs-fapi <openid-specs-fapi at lists.
>> openid.net>
>>> Sent: 10 May 2018 21:50
>>> To: Financial API Working Group List
>>> Cc: Mike Schwartz; Nat Sakimura
>>> Subject: Re: [Openid-specs-fapi] Issue #140: New name for FAPI
>> (openid/fapi)
>>> +1 on "OpenID Enhanced" or "Enhanced OpenID"
>>>
>>> Although, there is the EAP WG (Enhanced Authentication Profile), so it
>>> might be a little confusing.
>>>
>>> And "Enhanced OpenID" doesn't have the same ring as "OpenID Plus" :)
>>>
>>> - Mike
>>>
>>>
>>> On 2018-05-10 15:30, John Bradley via Openid-specs-fapi wrote:
>>>> I think that the remaining things with FAPI in the name can be
>>>> explained in the spec.
>>>>
>>>> Changing the WG name is probably the most important part.
>>>>
>>>> I don’t have a problem with calling the specs Enhanced OpenID profile
>>>> or something like that while still having a X-FAPI header if we need
>>>> to.
>>>>
>>>> John B.
>>>>
>>>>> On May 2, 2018, at 1:12 AM, Nat Sakimura via Openid-specs-fapi
>>>>> <openid-specs-fapi at lists.openid.net> wrote:
>>>>>
>>>>> New issue 140: New name for FAPI
>>>>> https://bitbucket.org/openid/fapi/issues/140/new-name-for-fapi
>>>>>
>>>>> Nat Sakimura:
>>>>>
>>>>> In March Board meeting, the board requested the name for FAPI to be
>>>>> generalized so that it will match the wider applicability of the
>>>>> security profiles.
>>>>>
>>>>> This is a fair request but the catch is that the string 'fapi' is
>>>>> already used in the protocol parameters and we do not want to change
>>>>> it.
>>>>>
>>>>> Thus we have a constrained name search: the new name should have an
>>>>> acronym that would result in **FAPI**.
>>>>>
>>>>> This ticket collects some candidates on it.
>>>>>
>>>>> Some of the initial ideas:
>>>>>
>>>>> * Fully Assured Protection Interoperable
>>>>> * Fair Assurance Protection Interface
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Openid-specs-fapi mailing list
>>>>> Openid-specs-fapi at lists.openid.net
>>>>> http://lists.openid.net/mailman/listinfo/openid-specs-fapi
>>>> _______________________________________________
>>>> Openid-specs-fapi mailing list
>>>> Openid-specs-fapi at lists.openid.net
>>>> http://lists.openid.net/mailman/listinfo/openid-specs-fapi
>>> _______________________________________________
>>> Openid-specs-fapi mailing list
>>> Openid-specs-fapi at lists.openid.net
>>> http://lists.openid.net/mailman/listinfo/openid-specs-fapi
>>>
>>> Please consider the environment before printing this email.
>>>
>>> This email is from Open Banking Limited, Company Number 10440081.  Our
>> registered and postal address is 2 Thomas More Square, London, E1W 1YN.
>> Any views or opinions are solely those of the author and do not necessarily
>> represent those of Open Banking Limited.
>>> This email and any attachments are confidential and are intended for the
>> above named only.  They may also be legally privileged or covered by other
>> legal rights and rules.  Unauthorised dissemination or copying of this
>> email and any attachments, and any use or disclosure of them, is strictly
>> prohibited and may be illegal.  If you have received them in error, please
>> delete them and all copies from your system and notify the sender
>> immediately by return email.
>>> _______________________________________________
>>> Openid-specs-fapi mailing list
>>> Openid-specs-fapi at lists.openid.net
>>> http://lists.openid.net/mailman/listinfo/openid-specs-fapi
>>
>>
>> _______________________________________________
>> Openid-specs-fapi mailing list
>> Openid-specs-fapi at lists.openid.net
>> http://lists.openid.net/mailman/listinfo/openid-specs-fapi
>>
>>
>


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4002 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.openid.net/pipermail/openid-specs-fapi/attachments/20180511/23127099/attachment-0001.p7s>


More information about the Openid-specs-fapi mailing list