[Openid-specs-fapi] Pushed Request Object as IETF Draft

Steinar Noem steinar at udelt.no
Wed Sep 4 17:25:30 UTC 2019

I think it makes a lot of sense. It will definitely make things a lot
easier on the client side, both for implementation and potentially due to
infrastructural limitations.
We are trying out request objects in OIDC and have found that size matters,
so that's another benefit.

- Steinar

ons. 4. sep. 2019 kl. 17:30 skrev Torsten Lodderstedt via Openid-specs-fapi
<openid-specs-fapi at lists.openid.net>:

> Hi all,
> I would like to bring the Pushed Request Object draft to the OAuth WG.
> Daniel presented this idea during the last IETF meeting to the OAuth WG and
> there was interest in the topic.
> What’s your opinion?
> Anyone objecting against this step?
> best regards,
> Torsten. _______________________________________________
> Openid-specs-fapi mailing list
> Openid-specs-fapi at lists.openid.net
> http://lists.openid.net/mailman/listinfo/openid-specs-fapi

Vennlig hilsen

Steinar Noem
Partner Udelt AS

| steinar at udelt.no | hei at udelt.no  | +47 955 21 620 | www.udelt.no |
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-fapi/attachments/20190904/7d31a106/attachment.html>

More information about the Openid-specs-fapi mailing list