[Openid-specs-fapi] Verification: non-compliant JWT audience

Nat Sakimura nat at sakimura.org
Wed Sep 27 10:28:45 UTC 2017


 

So, shall we talk about this in the next call, that is happening in a
few hours? 

---
Nat Sakimura
Research Fellow, Nomura Research Institute
Chairman of the Board, OpenID Foundation

On 2017-09-26 06:28, Brian Campbell via Openid-specs-fapi wrote: 

> I tend to agree with John here. The OB software statement probably shouldn't have an audience at all or, if it does, some kind of logical audience for all UK-Open banking participants would be more appropriate. 
> 
> The jose4j library does allow the ability to override the rules set out in https://tools.ietf.org/html/rfc7519#section-4.1.3 [1] but the intent is to turn off the default processing and enable more complex or application specific audience processing by plugging in customized claim validation in specialized cases that need it. Although it can be abused, It's not intended to allow for non compliant behavior. 
> 
> On Fri, Sep 22, 2017 at 5:50 PM, John Bradley via Openid-specs-fapi <openid-specs-fapi at lists.openid.net> wrote:
> 
> I guess the other question is if the software statement should have an audience. Nothing in JWT requires on. Or you could have a logical audience for UK-Open banking participants that they could all recognize. That would keep other people from accidentally trying to process it. 
> 
> John B.
> 
> On Sep 22, 2017, at 7:53 PM, Pamela Dingle via Openid-specs-fapi <openid-specs-fapi at lists.openid.net> wrote: 
> 
> Hi FAPI'ers, 
> 
> Can anyone here comment on whether they use or make technology that CANNOT override the standard RFC7519 JWT audience validation requirements? 
> 
> I know that the jose4j library allows the ability to override the rules set out in https://tools.ietf.org/html/rfc7519#section-4.1.3 [1] but I don't know if that is a common feature of other libraries. As I read those rules, any entity that receives a JWT with an aud claim populated but which does not have the entity itself listed as a recipient should reject that JWT. 
> 
> In this case we are talking about validating software statements in a dynamic client requests -- if the software statement is generated with an audience set to be the client requesting the software statement, technically every AS the client tries to post that statement to should reject the statement, since the aud claim does not reference them directly. Any opinions on whether at the end of the day this is a serious compliance issue (or not), and/or a real problem for implementers (or not) would be welcome. 
> 
> Cheers, 
> 
> Pamela 
> 
> -- 
> 
> [2]
> 
> Pam Dingle 
> Principal Technical Architect 
> pdingle at pingidentity.com 
> w: +1 303.999.5890 [3] 
> c: +1 303.999.5890 [3] 
> 
> Connect with us:
> [4] [5] [6] [7] [8] [9] [10]
> 
> [11] _CONFIDENTIALITY NOTICE: This email may contain confidential and privileged material for the sole use of the intended recipient(s). Any review, use, distribution or disclosure by others is strictly prohibited. If you have received this communication in error, please notify the sender immediately by e-mail and delete the message and any file attachments from your computer. Thank you.________________________________________________
> Openid-specs-fapi mailing list
> Openid-specs-fapi at lists.openid.net
> http://lists.openid.net/mailman/listinfo/openid-specs-fapi [12] 
> _______________________________________________
> Openid-specs-fapi mailing list
> Openid-specs-fapi at lists.openid.net
> http://lists.openid.net/mailman/listinfo/openid-specs-fapi [12]

_CONFIDENTIALITY NOTICE: This email may contain confidential and
privileged material for the sole use of the intended recipient(s). Any
review, use, distribution or disclosure by others is strictly
prohibited. If you have received this communication in error, please
notify the sender immediately by e-mail and delete the message and any
file attachments from your computer. Thank you._ 

_______________________________________________
Openid-specs-fapi mailing list
Openid-specs-fapi at lists.openid.net
http://lists.openid.net/mailman/listinfo/openid-specs-fapi [12]

 

Links:
------
[1] https://tools.ietf.org/html/rfc7519#section-4.1.3
[2] https://www.pingidentity.com/
[3] tel:(303)%20999-5890
[4]
https://www.glassdoor.com/Overview/Working-at-Ping-Identity-EI_IE380907.11,24.htm
[5] https://www.linkedin.com/company/21870
[6] https://twitter.com/pingidentity
[7] https://www.facebook.com/pingidentitypage
[8] https://www.youtube.com/user/PingIdentityTV
[9] https://plus.google.com/u/0/114266977739397708540
[10] https://www.pingidentity.com/en/blog.html
[11] https://www.pingidentity.com/en/lp/identify-2017.html
[12] http://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/20170927/19f7b6df/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: blocked.gif
Type: image/gif
Size: 118 bytes
Desc: not available
URL: <http://lists.openid.net/pipermail/openid-specs-fapi/attachments/20170927/19f7b6df/attachment.gif>


More information about the Openid-specs-fapi mailing list