[Openid-specs-fapi] Working Group Last Call - JARM

[Torsten Lodderstedt]

> Am 02.07.2022 um 09:54 schrieb Nat Sakimura via Openid-specs-fapi <openid-specs-fapi at lists.openid.net>:

Hi Nat,

thanks for your review.

> 
> 
> Gee. Was that May? 
> 
> So, there are a few points that need to be fixed or at least I would like to discuss and verify. 
> 
> * JARM appears to only define behavior for response type code and token, but the treatment of ID Token comes up later saying it needs to be encrypted. Perhaps the reference can be removed. 

That text makes encryption a MUST, which goes far beyond core and even FAPI. I agree with your proposal to remove it.

> 
> * alg=none does not seem to be prohibited. This nullify the value of JARM so it should introduce a requirement prohibiting it and the client side check as well. 

I agree.

> 
> * The verification process by the client does not use normative language. 

Do you refer to clause 1 of section 2.4? I’m asking since the rest of this section has normative language.

> 
> * Protocol run identifier such as nonce or PKCE should be required.  

you mean and alignment with security BCP and FAPI? I would rather prefer to stay away from stating things already covered in other places (and might change). This is a small addition to OAuth to allow for signing and encryption of the response. The content of the response should be defined wherever the response type is defined or refined.

> 
> I will file those issues later when I get back to my computer. 

thanks 

> 
> Best,
> 
> Nat Sakamura 
> 
> 
> 2022年6月1日(水) 23:53 Dave Tonge via Openid-specs-fapi <openid-specs-fapi at lists.openid.net>:
>> Bumping this email as discussed on the call
>> 
>>> On Wed, 25 May 2022 at 17:15, Dave Tonge <dave.tonge at momentumft.co.uk> wrote:
>>> Dear FAPI Working Group
>>> 
>>> We would like to start the working group last call for JWT Secured Authorization Response Mode for OAuth 2.0 (JARM)
>>> 
>>> The latest draft is available here:
>>> https://openid.bitbucket.io/fapi/openid-fapi-jarm.html
>>> 
>>> Please provide your feedback by the 1st of June so that we can start the public review period.
>>> 
>>> Thank you
>>> 
>>> 
>>> -- 
>>> Dave Tonge
>>> FAPI WG Co-Chair
>>> 
>> 
>> 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 https://register.fca.org.uk/. Moneyhub Financial Technology is registered in England & Wales, company registration number 06909772. Registered address: C/O Roxburgh Milkins Limited Merchants House North, Wapping Road, Bristol, United Kingdom, BS1 4RW, United Kingdom. Moneyhub Financial Technology Limited 2022 © Moneyhub Enterprise.
>> 
>> 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.
>> 
>> 
>> _______________________________________________
>> Openid-specs-fapi mailing list
>> Openid-specs-fapi at lists.openid.net
>> https://lists.openid.net/mailman/listinfo/openid-specs-fapi
> _______________________________________________
> Openid-specs-fapi mailing list
> Openid-specs-fapi at lists.openid.net
> https://lists.openid.net/mailman/listinfo/openid-specs-fapi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-fapi/attachments/20220703/91aa0f69/attachment-0001.html>