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

Issues

Filter by:

Advanced search

Issues (26–50 of 693)

Title T P Status Votes Assignee Milestone Created Updated Actions
#693: MTLS section readability
FAPI2: Security Profile
bug major resolved
#685: Use of TLS 1.2 Ciphers
FAPI2: Security Profile
bug major resolved
#698: Vulnerability in TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
FAPI2: Security Profile
bug major resolved
#697: FAPI2SP have links to https://openid.bitbucket.io/
FAPI2: Security Profile
bug major resolved
#689: FAPI + FedCM
bug major open
#692: CAA records
FAPI2: Security Profile
bug major resolved
#395: Unclear formatting in FAPI1-Baseline final client section
FAPI 1: Baseline
bug major resolved
#622: Review FAPI1 security considerations for clarity
FAPI 1: Advanced
bug major resolved
#677: (Review Title) in the section headings
FAPI2: Attacker Model
bug major resolved
#681: See Clause 9 for normative references in Clause 2 wrong
FAPI2: Attacker Model
bug major resolved
#691: General (Review title)
FAPI2: Attacker Model
bug minor resolved
#656: Create terms and definition as well as the abbreviations for the attacker model document
FAPI2: Attacker Model
bug major resolved
#688: Simplifying the usage of FAPI-CIBA and FAPI 2 profiles together
CIBA
proposal major new
#658: allow use of a future fully specified JWS algorithm identifier for EdDSA w/ Ed25519
FAPI2: Security Profile
enhancement major resolved
#674: length of nonce tested in OP conformance tests
FAPI2: Security Profile
bug major resolved 1
#670: Use of FAPI with mandatory MTLS
FAPI2: Security Profile
bug major resolved
#651: Avoid "should be" and "shall be" where possible
FAPI2: Security Profile
bug major resolved
#679: (ed) replace (this) specification with (this) document
FAPI2: Security Profile
bug major resolved
#642: Continuation of #619 -- Add some text to make the readers aware of the caveats.
FAPI2: Security Profile
bug major resolved
#550: Should Network Layer Protections be made server-side enforced?
FAPI2: Security Profile
bug major resolved
#682: Clarify allowed use of `state` and required CSRF protection in FAPI 2.0 SP
FAPI2: Security Profile
proposal major resolved
#683: minimum length for EC keys?
FAPI2: Security Profile
bug minor resolved
#686: CIBA response parameters in PSD2 TPP use-cases
CIBA
enhancement major new
#638: Add some more text to Introduction
FAPI2: Security Profile
bug major resolved
#687: FAPI-CIBA shall be inheriting these sections from a chosen security profile (FAPI 1 or FAPI 2)?
CIBA
proposal major new
  2. 1
  3. 2
  4. 3
  5. 4
  6. 5
  7. 6
  8. …
  9. 27
  10. 28