1. OpenID Foundation Avatar OpenID Foundation
  2. WGs
  3. fapi

Issues

Filter by:

Advanced search

Issues (1–25 of 498)

Title T P Status Votes Assignee Milestone Created Updated Actions
#392: Copyright template is wrong
FAPI 1: Advanced
bug blocker resolved
#366: Remove Warning from Part 1 and 2 of FAPI 1.0
FAPI 1: Advanced
task blocker resolved
#144: Apply the new name to the Part 1 and 2
FAPI 1: Advanced
bug blocker resolved
#354: Numbering: FAPI Part 2 Section 5.2
FAPI 1: Advanced
bug critical resolved
#449: Field name and type for resources
Grant Management
bug critical resolved
#455: Impact of grant_management_action=update on AT implementation and introspection
Grant Management
bug critical resolved
#523: Rotation of Refresh token - Compromised client highlighted by AU - CDR Independent review.
FAPI2: Security Profile
proposal critical resolved
#505: Create security and privacy consideration for FAPI 2.0 Security Profile
FAPI2: Security Profile
bug critical resolved
#90: Create a sensible privacy consideration section
FAPI 1: Advanced
bug critical resolved
#395: Unclear formatting in FAPI1-Baseline final client section
FAPI 1: Baseline
bug major resolved
#622: Review FAPI1 security considerations for clarity
FAPI 1: Advanced
bug major resolved
#677: (Review Title) in the section headings
FAPI2: Attacker Model
bug major resolved
#681: See Clause 9 for normative references in Clause 2 wrong
FAPI2: Attacker Model
bug major resolved
#656: Create terms and definition as well as the abbreviations for the attacker model document
FAPI2: Attacker Model
bug major resolved
#658: allow use of a future fully specified JWS algorithm identifier for EdDSA w/ Ed25519
FAPI2: Security Profile
enhancement major resolved
#674: length of nonce tested in OP conformance tests
FAPI2: Security Profile
bug major resolved 1
#670: Use of FAPI with mandatory MTLS
FAPI2: Security Profile
bug major resolved
#651: Avoid "should be" and "shall be" where possible
FAPI2: Security Profile
bug major resolved
#679: (ed) replace (this) specification with (this) document
FAPI2: Security Profile
bug major resolved
#642: Continuation of #619 -- Add some text to make the readers aware of the caveats.
FAPI2: Security Profile
bug major resolved
#550: Should Network Layer Protections be made server-side enforced?
FAPI2: Security Profile
bug major resolved
#682: Clarify allowed use of `state` and required CSRF protection in FAPI 2.0 SP
FAPI2: Security Profile
proposal major resolved
#638: Add some more text to Introduction
FAPI2: Security Profile
bug major resolved
#678: (ed) Privacy considerations is a top level clause while Security considerations is a second level subclause
FAPI2: Security Profile
bug major resolved
#646: NOTE in 5.2.1 has "can"
FAPI2: Security Profile
bug major resolved
  2. 1
  3. 2
  4. 3
  5. 4
  6. 5
  7. 6
  8. …
  9. 19
  10. 20