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

Issues

Filter by:

Advanced search

Issues (1–25 of 26)

Title T P Status Votes Assignee Milestone Created Updated Actions
#216: TLS_ECDHE_ECDSA cipher suites
FAPI 1: Advanced
proposal major resolved
#239: FAPI part 2 should mention/require discovery?
FAPI 1: Advanced
proposal major resolved
#172: Add Guidance for the use of FAPI for payments
FAPI 1: Advanced
proposal major resolved
#101: JWS signature algorithms for RW
FAPI 1: Advanced
enhancement minor resolved
#209: Ciphers
FAPI 1: Advanced
enhancement major resolved
#622: Review FAPI1 security considerations for clarity
FAPI 1: Advanced
bug major new
#394: Old links to part 1 / part 2 in git repo no longer work
FAPI 1: Advanced
bug major closed
#90: Create a sensible privacy consideration section
FAPI 1: Advanced
bug critical resolved
#168: (ed) Normative Reference: Most of them are not quoted with "shall"
FAPI 1: Advanced
bug minor resolved
#303: Proof Read Parts 1 and 2
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
#194: Security considerations when two (oauth-mtls?) clients use same key
FAPI 1: Advanced
bug 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
#279: document key selection algorithm
FAPI 1: Advanced
bug 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
#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
  2. 1
  3. 2