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

Issues

Filter by:

Advanced search

Issues (351–375 of 522)

Title T P Status Votes Assignee Milestone Created Updated Actions
#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
#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
#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
#110: more definition of s_hash
FAPI 1: Advanced
bug major resolved
#274: Require HSTS for authorization server
FAPI 1: Advanced
bug major resolved
#180: Behaviour of AS when presented with a non-uuid x-fapi-interaction-id is not clearly defined
FAPI 1: Baseline
bug major resolved
#182: 128 bits of entropy cannot give probability of guessing below 2^-160
FAPI 1: Baseline
bug minor resolved
#240: FAPI-R: length/entropy of authorization code / refresh token / client_secret
FAPI 1: Baseline
enhancement minor resolved
  2. 1
  3. 2
  4. …
  5. 13
  6. 14
  7. 15
  8. 16
  9. 17
  10. 18
  11. 19
  12. 20
  13. 21