FAPI2 Release Communication
Issue #348
resolved
We discussed on the last Atlantic call that we need to take care with the communication around the release of FAPI 2.0.
There was discussion of a “frequently asked questions”, where we could discuss why an ecosystem may prefer to chose FAPI1 vs FAPI2.
We agreed to start work on a Google Doc around this. I’ve created a doc here: https://docs.google.com/document/d/1Fo44L_wM4TIMxF3f1xowNWdlqEqZkZdjAyd1pAtab9U/edit?usp=sharing
Currently anyone with the link has edit access, so please feel free to start adding questions / answers.
Comments (5)
-
-
Hi, Authlete 2.2 now supports “OAuth 2.0 Authorization Server Issuer Identifier in Authorization Response”.
-
Thanks Dave .. I have added few comments.
Looks great otherwise…
-
reporter - changed status to resolved
-
- changed component to FAPI2: Security Profile
- Log in to comment
Thanks Dave! I’ve added a few suggestions to the google doc.