|
16 | 16 |
|
17 | 17 | <p>The core FAPI functionality is split into two documents, with a third that describes the attacker model</p> |
18 | 18 | <ul> |
19 | | - <li><a href="https://openid.bitbucket.io/fapi/fapi-2_0-security-profile.html">FAPI 2.0 Security Profile</a></li> |
20 | | - <li><a href="https://openid.bitbucket.io/fapi/fapi-2_0-message-signing.html">FAPI 2.0 Message Signing</a></li> |
21 | | - <li><a href="https://openid.bitbucket.io/fapi/fapi-2_0-attacker-model.html">FAPI 2.0 Attacker Model</a></li> |
| 19 | + <li><a href="https://openid.net/specs/fapi-security-profile-2_0-final.html">FAPI 2.0 Security Profile</a> (Final)</li> |
| 20 | + <li><a href="https://openid.net/specs/fapi-attacker-model-2_0-final.html">FAPI 2.0 Attacker Model</a> (Final)</li> |
| 21 | + <li><a href="https://openid.bitbucket.io/fapi/fapi-2_0-message-signing.html">FAPI 2.0 Message Signing</a> (Draft)</li> |
22 | 22 | </ul> |
23 | 23 |
|
24 | 24 | <p>Specifications Referenced by FAPI</p> |
25 | 25 | <ul> |
26 | | - <li><a href="https://www.rfc-editor.org/rfc/rfc6749">RFC 6749</a> - OAuth 2.0 Framework</li> |
27 | | - <li><a href="https://www.rfc-editor.org/rfc/rfc6750">RFC 6750</a> - OAuth 2.0 Bearer Token Usage</li> |
28 | | - <li><a href="https://www.rfc-editor.org/rfc/rfc7521">RFC 7521</a> - Assertion Framework for OAuth 2.0 Client Authentication and Authorization Grants</li> |
29 | | - <li><a href="https://www.rfc-editor.org/rfc/rfc7523">RFC 7523</a> - JWT Profile for OAuth 2.0 Client Authentication and Authorization Grants</li> |
30 | | - <li><a href="https://www.rfc-editor.org/rfc/rfc7636">RFC 7636</a> - Proof Key for Code Exchange</li> |
31 | | - <li><a href="https://www.rfc-editor.org/rfc/rfc7662">RFC 7662</a> - OAuth 2.0 Token Introspection</li> |
32 | | - <li><a href="https://www.rfc-editor.org/rfc/rfc8252">RFC 8252</a> - OAuth 2.0 for Native Apps BCP</li> |
33 | | - <li><a href="https://www.rfc-editor.org/rfc/rfc8414">RFC 8414</a> - OAuth 2.0 Authorization Server Metadata</li> |
34 | | - <li><a href="https://www.rfc-editor.org/rfc/rfc8705">RFC 8705</a> - Mutual TLS Client Authentication and Certificate-Bound Access Tokens</li> |
35 | | - <li><a href="https://www.rfc-editor.org/rfc/rfc8725">RFC 8725</a> - JSON Web Token Best Practices</li> |
36 | | - <li><a href="https://www.rfc-editor.org/rfc/rfc9101">RFC 9101</a> - JWT Secured Authorization Request (JAR)</li> |
37 | | - <li><a href="https://www.rfc-editor.org/rfc/rfc9126">RFC 9126</a> - Pushed Authorization Requests (PAR)</li> |
38 | | - <li><a href="https://www.rfc-editor.org/rfc/rfc9207">RFC 9207</a> - OAuth 2.0 Authorization Server Issuer Identification</li> |
39 | | - <li><a href="https://datatracker.ietf.org/doc/html/draft-ietf-oauth-dpop">DPoP</a> - Demonstrating Proof-of-Possession at the Application Layer</li> |
40 | | - <li><a href="https://datatracker.ietf.org/doc/html/draft-ietf-oauth-jwt-introspection-response">JWT Response for OAuth Token Introspection</a></li> |
41 | | - <li><a href="https://www.rfc-editor.org/rfc/rfc9421">RFC 9421</a> - HTTP Message Signatures</li> |
42 | | - <li><a href="https://www.rfc-editor.org/rfc/rfc9530">RFC 9530</a> - HTTP Digest Headers</li> |
| 26 | + <li><a href="https://datatracker.ietf.org/doc/html/rfc6749">RFC 6749</a> - OAuth 2.0 Framework</li> |
| 27 | + <li><a href="https://datatracker.ietf.org/doc/html/rfc6750">RFC 6750</a> - OAuth 2.0 Bearer Token Usage</li> |
| 28 | + <li><a href="https://datatracker.ietf.org/doc/html/rfc7521">RFC 7521</a> - Assertion Framework for OAuth 2.0 Client Authentication and Authorization Grants</li> |
| 29 | + <li><a href="https://datatracker.ietf.org/doc/html/rfc7523">RFC 7523</a> - JWT Profile for OAuth 2.0 Client Authentication and Authorization Grants</li> |
| 30 | + <li><a href="https://datatracker.ietf.org/doc/html/rfc7636">RFC 7636</a> - Proof Key for Code Exchange</li> |
| 31 | + <li><a href="https://datatracker.ietf.org/doc/html/rfc7662">RFC 7662</a> - OAuth 2.0 Token Introspection</li> |
| 32 | + <li><a href="https://datatracker.ietf.org/doc/html/rfc8252">RFC 8252</a> - OAuth 2.0 for Native Apps BCP</li> |
| 33 | + <li><a href="https://datatracker.ietf.org/doc/html/rfc8414">RFC 8414</a> - OAuth 2.0 Authorization Server Metadata</li> |
| 34 | + <li><a href="https://datatracker.ietf.org/doc/html/rfc8705">RFC 8705</a> - Mutual TLS Client Authentication and Certificate-Bound Access Tokens</li> |
| 35 | + <li><a href="https://datatracker.ietf.org/doc/html/rfc8725">RFC 8725</a> - JSON Web Token Best Practices</li> |
| 36 | + <li><a href="https://datatracker.ietf.org/doc/html/rfc9101">RFC 9101</a> - JWT Secured Authorization Request (JAR)</li> |
| 37 | + <li><a href="https://datatracker.ietf.org/doc/html/rfc9126">RFC 9126</a> - Pushed Authorization Requests (PAR)</li> |
| 38 | + <li><a href="https://datatracker.ietf.org/doc/html/rfc9207">RFC 9207</a> - OAuth 2.0 Authorization Server Issuer Identification</li> |
| 39 | + <li><a href="https://datatracker.ietf.org/doc/html/rfc9449">RFC 9449</a> - DPoP: Demonstrating Proof-of-Possession at the Application Layer</li> |
| 40 | + <li><a href="https://datatracker.ietf.org/doc/html/rfc9421">RFC 9421</a> - HTTP Message Signatures</li> |
| 41 | + <li><a href="https://datatracker.ietf.org/doc/html/rfc9530">RFC 9530</a> - HTTP Digest Headers</li> |
| 42 | + <li><a href="https://datatracker.ietf.org/doc/html/rfc9700">RFC 9700</a> - Best Current Practice for OAuth 2.0 Security</li> |
| 43 | + <li><a href="https://datatracker.ietf.org/doc/html/rfc9701">RFC 9701</a> - JWT Response for OAuth Token Introspection</li> |
43 | 44 | <li><a href="https://openid.net/specs/oauth-v2-jarm.html">JWT Secured Authorization Response Mode for OAuth 2.0 (JARM)</a></li> |
44 | 45 | </ul> |
45 | 46 |
|
46 | 47 | <p>More resources |
47 | 48 | <ul> |
48 | 49 | <li><a href="https://identityunlocked.auth0.com/public/49/Identity%2C-Unlocked.--bed7fada/d847cfb7">Exploring Financial-Grade API (FAPI) with Torsten</a> (Identity Unlocked Podcast)</li> |
49 | 50 | <li><a href="https://www.linkedin.com/pulse/fapi-20-security-profile-simpler-yes-wait-compulsory-standardised-">FAPI 2.0: Security Profile (Simpler Security, Yes!)</a> (Raidiam)</li> |
50 | | - <li><a href="https://openid.bitbucket.io/fapi/">All OpenID FAPI Working Group Drafts</a></li> |
| 51 | + <li><a href="https://openid.net/wg/fapi/specifications/">All OpenID FAPI Working Group Drafts</a></li> |
51 | 52 | </ul> |
52 | 53 | </p> |
53 | 54 |
|
|
0 commit comments