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

Issues

Filter by:

Advanced search

Issues (126–150 of 177)

Title T P Status Votes Assignee Milestone Created Updated Actions
#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
#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
#270: JARM+FAPI-RW+openid client session binding
FAPI 1: Advanced
bug major resolved
#154: Behaviour of AS undefined if no acr claim supplied by client
FAPI 1: Advanced
bug major resolved
#247: Make JARM equal alternative
FAPI 1: Advanced
enhancement major resolved
#281: update MTLS reference to point at RFC
FAPI 1: Advanced
bug major resolved
#163: more description of the security model
FAPI 1: Advanced
bug minor resolved
#275: Adopt PAR & RAR as recommended way to convey authorization data
FAPI 1: Advanced
bug major resolved
#158: FAPI part 2 - request object for public clients (signing key?)
FAPI 1: Advanced
bug major resolved
#252: Question about accessing UserInfo endpoint after ID token expiration
FAPI 1: Advanced
proposal major resolved
#268: [ACDS] Response regarding OIDC Dynamic Registration / SSA
FAPI 1: Advanced
task major resolved
#171: R+W Public Client Support for RW should be a MAY not a SHOULD
FAPI 1: Advanced
enhancement major resolved
#167: (ed) 5.2.3 - Last Para should be a numbered bullet
FAPI 1: Advanced
bug major resolved
#149: Make it clear that the entire flow is OIDC Hybrid Flow (related to #155)
FAPI 1: Advanced
bug major resolved
#221: FAPI-RW ID2 needs some further tweaks for JARM
FAPI 1: Advanced
bug major resolved
#209: Ciphers
FAPI 1: Advanced
enhancement major resolved
#172: Add Guidance for the use of FAPI for payments
FAPI 1: Advanced
proposal major resolved
  2. 1
  3. 2
  4. 3
  5. 4
  6. 5
  7. 6
  8. 7
  9. 8