[OAUTH-WG] Question regarding RFC 8628

2019-11-18 Thread Robache Hervé
Dear all We are considering using RFC8628 for a specific use case that is related to the version 2 of Payment Service Directive in Europe (PSD2). The purpose of the work is to provide a decoupled authentication flow for a payment Service User (PSU) aiming to grant access to a Third Party Provid

Re: [OAUTH-WG] Question regarding RFC 8628

2019-11-26 Thread Robache Hervé
Thanks Torsten, I didn't notice this point in CIBA. Sorry about asking a so silly question. Hervé -Message d'origine- De : Torsten Lodderstedt [mailto:tors...@lodderstedt.net] Envoyé : mardi 26 novembre 2019 11:33 À : Robache Hervé Cc : Joseph Heenan; oauth@ietf.org Objet :

[OAUTH-WG] Question regarding RFC 7592

2019-09-12 Thread Robache Hervé
Hi RFC 7592 introduces a « Registration Access Token ». Are this token and the way to get it similar to what is specified as “Initial Access Token” in RFC 7591/Appendix A ? If so, can the Open Dynamic Client Registration (RFC7591/A.1.1) be extrapolated to RFC7592 as the same way? Thanks in ad

Re: [OAUTH-WG] Question regarding RFC 7592

2019-09-13 Thread Robache Hervé
...@curity.io] Envoyé : ven. 13 13:30 À : Robache Hervé Cc : oauth@ietf.org Objet : Re: [OAUTH-WG] Question regarding RFC 7592 No. The initial access token is issued by the AS when registration is protected (appendix 1.2 in RFC 7591). As stated in section 1.2, the method and means by which this is

Re: [OAUTH-WG] Question regarding RFC 7592

2019-10-14 Thread Robache Hervé
Dear all Thanks for your answers. I understand that RFC7592/§3 should be taken into account for enhancing the Client Information Response of RFC7591. Best regards Hervé De : Travis Spencer [mailto:travis.spen...@curity.io] Envoyé : mercredi 18 septembre 2019 10:56 À : Robache Hervé Cc : oauth