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

Issues

Filter by:

Advanced search

Issues (51–75 of 119)

Title T P Status Votes Assignee Milestone Created Updated Actions
#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
#298: Change "holder of key" to "sender constrained"
FAPI 1: Advanced
bug major resolved
#202: authorization code and refresh token must be holder of key bound
FAPI 1: Advanced
bug major resolved
#207: RS256 vs PS256 (again)
FAPI 1: Advanced
bug major resolved
#251: refresh token expiry time
FAPI 1: Advanced
enhancement major resolved
#205: Add requirement for Client to verify state matches session
FAPI 1: Advanced
bug major resolved
#227: Add intro to FAPI RW - to explain that we don't support public clients
FAPI 1: Advanced
bug major resolved
#299: "In addition, the confidential client for write operations" causes confusion
FAPI 1: Advanced
bug major resolved
#203: Guidance around jwks and jwks_uri
FAPI 1: Advanced
bug major resolved
  2. 1
  3. 2
  4. 3
  5. 4
  6. 5