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

Issues

Filter by:

Advanced search

Issues (326–350 of 509)

Title T P Status Votes Assignee Milestone Created Updated Actions
#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
#207: RS256 vs PS256 (again)
FAPI 1: Advanced
bug major resolved
#251: refresh token expiry time
FAPI 1: Advanced
enhancement major resolved
#133: Two documents are labelled as part 3
Part 3: Open Data
bug major duplicate
#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
#277: FAPI-RW: Is disallowing signed id_tokens allowed? (i.e. always used signed+encrypted)
FAPI 1: Advanced
bug major resolved
#300: 5.2.3. Public client should be renamed to 5.2.3. Mobile client
FAPI 1: Advanced
bug major invalid
  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