[Openid-specs-fapi] External : FW: OBE JWS Profile - Version 0.10b for Approval

Brian Campbell bcampbell at pingidentity.com
Fri Sep 18 19:49:50 UTC 2020

On Thu, Sep 17, 2020 at 3:01 AM Ralph Bragg via Openid-specs-fapi <
openid-specs-fapi at lists.openid.net> wrote:

> One area that’s already been raised briefly during FAPI WG discussions, is
> where does OIDF / OpenID Connect Core see the intersection of this and
> other json signing specifications with the structures already defined for
> id_tokens and Authorization Request objects and the like.

Most/many of those structures need to traverse through the browser and so
the signature has to cover the content of the message for more than a
single HTTP message. So I'm not sure what the intersection is?

_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._
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-fapi/attachments/20200918/1d1aa722/attachment.html>

More information about the Openid-specs-fapi mailing list