[Openid-specs-fapi] Title change of Part 1 and Part 2.

Torsten Lodderstedt torsten at lodderstedt.net
Wed Nov 6 15:47:55 UTC 2019



> On 6. Nov 2019, at 16:07, Dave Tonge <dave.tonge at momentumft.co.uk> wrote:
> 
> We discussed the name change on the call and agreed to do some work on the attacker model.

+1 

> Here is the relevant issue on the FAPI issue tracker: https://bitbucket.org/openid/fapi/issues/163/more-description-of-the-security-model
> 
> It would be good to get some feedback on it.

Working on it :-)

> 
> Thanks
> 
> Dave
> 
> On Sun, 27 Oct 2019 at 14:50, Torsten Lodderstedt via Openid-specs-fapi <openid-specs-fapi at lists.openid.net> wrote:
> 
> 
>> Am 25.10.2019 um 03:15 schrieb Tatsuo Kudo via Openid-specs-fapi <openid-specs-fapi at lists.openid.net>:
>> 
>> 
>> I tend to explain the part 1 and 2 like:
>> 
>> 	• Part 1: OAuth 2.0 deployment practice + OAuth 2.0 extension specs
>> 	• Part 2: Part 1 + OIDC deployment practice + OIDC extension specs
>> So how about:
>> 
>> 	• Part 1: FAPI OAuth 2.0 Profile (FAPI-OAuth)
>> 	• Part 2: FAPI OpenID Connect Profile (FAPI-OIDC)
> As Nat described, the idea is to have security profiles on certain levels, both for OAuth. OpenID can be done with either profiles.
> 
> Right now read and read/write do not have a clear definition in terms of security protection goals and attacker model. The first idea is to make “substantial” (medium) the profile ensuring authenticity of all parties (e.g. client authentication) and preventing any sort of replay (PKCE & sender constrained tokens). “High” should go further and add application level non-repudiation.
> 
> best regards,
> Torsten.
>> Just my 2c.
>> 
>> Tatsuo.
>> 
>> 
>> 
>> On 2019/10/25 0:34, Nat Sakimura via Openid-specs-fapi wrote:
>>> Hi 
>>> 
>>> Back in the IIW, I discussed with Torsten about the potential title change of Part 1 and Part 2. Currently, they are Read Only and Read&Write respectively but there are cases where the read only data is very sensitive while write operation is not of high value. 
>>> 
>>> Thus, we agreed that the current name may not be representing the real intention: Medium and High security profile respectively. 
>>> 
>>> During the discussion, we came up with the name: 
>>> 
>>> - Substantial (for Part 1) 
>>> - High (for Part 2) 
>>> 
>>> It follows eIDAS marking. 
>>> 
>>> More details are recorded in the ticket #271. 
>>> 
>>> https://bitbucket.org/openid/fapi/issues/271/rename-and-adjust-fapi-profiles 
>>> 
>>> The participants in the Oct. 9 call all agreed to it. 
>>> This mail is to solicit wider opinions on it. 
>>> 
>>> Please let us know of your opinions. 
>>> 
>>> Best, 
>>> 
>>> Nat Sakimura 
>>> Chair, FAPI WG. 
>>> _______________________________________________ 
>>> 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
> 
> 
> -- 
> Dave Tonge
> CTO
> 
> Moneyhub Financial Technology, 5th Floor, 10 Temple Back, Bristol, BS1 6FL
> t: +44 (0)117 280 5120
> 
> Moneyhub Enterprise is a trading style of Moneyhub Financial Technology Limited which is authorised and regulated by the Financial Conduct Authority ("FCA"). Moneyhub Financial Technology is entered on the Financial Services Register (FRN 809360) at fca.org.uk/register. Moneyhub Financial Technology is registered in England & Wales, company registration number  06909772 .
> Moneyhub Financial Technology Limited 2018 ©
> 
> DISCLAIMER: This email (including any attachments) is subject to copyright, and the information in it is confidential. Use of this email or of any information in it other than by the addressee is unauthorised and unlawful. Whilst reasonable efforts are made to ensure that any attachments are virus-free, it is the recipient's sole responsibility to scan all attachments for viruses. All calls and emails to and from this company may be monitored and recorded for legitimate purposes relating to this company's business. Any opinions expressed in this email (or in any attachments) are those of the author and do not necessarily represent the opinions of Moneyhub Financial Technology Limited or of any other group company.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3923 bytes
Desc: not available
URL: <http://lists.openid.net/pipermail/openid-specs-fapi/attachments/20191106/c8676f1f/attachment-0001.p7s>


More information about the Openid-specs-fapi mailing list