- changed title to (ed) Need to add JARM in the introductions
(ed) Need to add JARM in the introductions
Issue #166
closed
Currently, it goes like:
Financial-grade API consists of the following parts:
- Part 1: Read-Only API Security Profile
- Part 2: Read and Write API Security Profile
- Client Initiated Backchannel Authentication Profile
Future parts may follow.
We need to add JARM. It does not have to be in this round, but we need to remember to update.
Comments (9)
-
reporter -
reporter -
assigned issue to
Currently, it goes like:
Financial-grade API consists of the following parts:
- Part 1: Read-Only API Security Profile
- Part 2: Read and Write API Security Profile
- Client Initiated Backchannel Authentication Profile
Future parts may follow.
We need to add JARM. It does not have to be in this round, but we need to remember to update.
-
assigned issue to
-
-
assigned issue to
Dave to update intros
-
assigned issue to
-
-
assigned issue to
-
assigned issue to
-
-
- changed status to closed
Merged in update-intros (pull request #185)
Update intros to mention JARM
- Update intros to mention JARM
Generally made them consistent, and removed references to Pushed Request Object as that's now PAR in the IETF OAuth WG.
closes
#166- Update README.md
Remove Pushed Request Object, add Implementation & Deployment advice.
Approved-by: Dave Tonge
→ <<cset fa3159bca357>>
-
reporter - changed component to Part 2: Advanced
-
reporter - changed component to FAPI 1 – Part 2: Advanced
-
reporter - changed component to FAPI 1: Advanced
- Log in to comment