[Openid-specs-fapi] Issue #171: R+W Public Client Support for RW should be a MAY not a SHOULD (openid/fapi)

Ralph Bragg issues-reply at bitbucket.org
Fri Sep 7 14:30:07 UTC 2018


New issue 171: R+W Public Client Support for RW should be a MAY not a SHOULD
https://bitbucket.org/openid/fapi/issues/171/r-w-public-client-support-for-rw-should-be

Ralph Bragg:

The verb for supporting public clients in Read is a SHOULD. No reference to public clients is made in RW, i believe the assumption was that public client support should be optional but it isnt explicitly stated.

Suggest, if this bug request is approved, a MAY override be added to RW so that ASPSPs  do not feel obliged to support public clients.

I'm aware that SHOULD can also be ignored with good reason as well but this causes some implementors confusion.




More information about the Openid-specs-fapi mailing list