Remove Public Client Support

[Dave Tonge]

We discussed removing public client support for part 2 in: https://bitbucket.org/openid/fapi/issues/158/fapi-part-2-request-object-for-public

I think we should consider removing it in part 1 as well. At the very least this clause will need to be removed or updated as its not that clear:

1. shall support [RFC7636] or the mechanisms defined in Financial-grade API - Part 2;

In addition I suggest that we have a clause recommending the dynamic registration of confidential clients for the "mobile app" use case.

[Joseph Heenan]

Dave started a thread on the mailing list on this topic: http://lists.openid.net/pipermail/openid-specs-fapi/2019-January/001212.html

[Nat Sakimura]

Remove

Shall support …

as stated as the second option.

[Nat Sakimura]

We discussed removing public client support for part 2 in: https://bitbucket.org/openid/fapi/issues/158/fapi-part-2-request-object-for-public

I think we should consider removing it in part 1 as well. At the very least this clause will need to be removed or updated as its not that clear:

1. shall support [RFC7636] or the mechanisms defined in Financial-grade API - Part 2;

In addition I suggest that we have a clause recommending the dynamic registration of confidential clients for the "mobile app" use case.

[Dave Tonge]

I believe we discussed sorting out the public client bit in part 2 first.

[Dave Tonge]

I propose we close this ticket

[Dave Tonge]

We agreed to close this ticket - any breaking changes like this will go into 2.0