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

Issues

Filter by:

Advanced search

Issues (326–350 of 522)

Title T P Status Votes Assignee Milestone Created Updated Actions
#305: Check if the documents listed in Normative Refernece are refered by "shall" or included in Clause 3
FAPI 1: Advanced
bug major duplicate
#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
#320: Pre-registration of redirect uris with PAR
FAPI 1: Advanced
bug major wontfix
#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
#124: More examples as an appendix
FAPI 1: Advanced
proposal major closed
#313: (ed) 8.8 has "MUST" and "MUST NOT"
FAPI 1: Advanced
bug major resolved
#304: Are duplicates of the response_type, and scope values necessary when using PAR?
FAPI 1: Advanced
bug major closed
#194: Security considerations when two (oauth-mtls?) clients use same key
FAPI 1: Advanced
bug major resolved
#224: FAPI certification conformance profile definitions needed
FAPI 1: Advanced
task major wontfix
#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
#307: FAPI-RW: Require pkce when using PAR
FAPI 1: Advanced
bug major closed
#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
#264: expand on privacy considerations for id_tokens returned in front channel
FAPI 1: Advanced
enhancement major closed
#166: (ed) Need to add JARM in the introductions
FAPI 1: Advanced
bug major closed
#262: should long lived access tokens be permitted
FAPI 1: Baseline
enhancement 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