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

Issues

Filter by:

Advanced search

Issues (326–350 of 512)

Title T P Status Votes Assignee Milestone Created Updated Actions
#333: Fix the broken link to ISO Directive 2
FAPI 1: Advanced
bug major resolved
#317: Part 1 'require the redirect_uri parameter' could have a better wording
FAPI 1: Baseline
bug major resolved
#340: treatment of authorization request parameters outside PAR
FAPI2: Security Profile
bug major resolved
#342: sender-constrained auth codes & refresh tokens: what does it mean?
FAPI2: Security Profile
bug major resolved
#344: "x-" isn't cool anymore
FAPI2: Security Profile
bug major resolved
#173: Mix-up mitigation (defence in depth)
FAPI2: Security Profile
proposal minor resolved
#323: Editorial: unclear language in TLS Considerations 8.5
FAPI 1: Advanced
enhancement trivial resolved
#329: FAPI 1.0 Part 1 and Part 2 Title
FAPI 1: Advanced
proposal major resolved
#322: Editorial: Section 5.2.2.2.1. Duplicate Clause?
FAPI 1: Advanced
task trivial resolved
#321: Editorial: Language describing acceptable token endpoint authentication mechanisms.
FAPI 1: Advanced
task trivial resolved
#324: Editorial: TLS 8.5 BCP195 not referenced in bibliography.
FAPI 1: Advanced
enhancement trivial resolved
#312: Clarify intended purpose of FAPI 1.0 profiles
FAPI 1: Advanced
bug major resolved
#303: Proof Read Parts 1 and 2
FAPI 1: Advanced
bug major resolved
#315: PAR certification question - must servers allow requests where scope/response_type only passed to PAR endpoint
FAPI 1: Advanced
bug major resolved
#318: Privacy consideration - "replay of long term grants at AS"
FAPI 1: Advanced
bug major resolved
#135: Confidential client needs a strong identity for the user to verify real world entity
FAPI 1: Advanced
enhancement major resolved
#314: FAPI-RW 1.0 certification tests using PAR
FAPI 1: Advanced
proposal major resolved
#313: (ed) 8.8 has "MUST" and "MUST NOT"
FAPI 1: Advanced
bug major resolved
#194: Security considerations when two (oauth-mtls?) clients use same key
FAPI 1: Advanced
bug major resolved
#239: FAPI part 2 should mention/require discovery?
FAPI 1: Advanced
proposal major resolved
#255: certification clarification request: location of discovery document
FAPI 1: Advanced
bug major resolved
#292: PKCE inconsistencies between Part 1 and Part 2
FAPI 1: Advanced
bug major resolved
#308: For info/feedback - new FAPI-RW ID2 certification tests
FAPI 1: Advanced
bug major resolved
#311: Is not many of the security consideration generic and not specific to FAPI Part 2?
FAPI 1: Advanced
bug major resolved
#279: document key selection algorithm
FAPI 1: Advanced
bug major resolved
  2. 1
  3. 2
  4. …
  5. 12
  6. 13
  7. 14
  8. 15
  9. 16
  10. 17
  11. 18
  12. 19
  13. 20
  14. 21