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

Issues

Filter by:

Advanced search

Issues (1–25 of 113)

Title T P Status Votes Assignee Milestone Created Updated Actions
#694: Refresh token clause readability
FAPI2: Security Profile
bug major new 1
#704: Consider recommendations from Cyber Safety Review Board report
FAPI2: Security Profile
bug major open
#703: Tweaks to BCP195 language
FAPI2: Security Profile
bug major open
#696: FAPI2SP should reference formal analysis
FAPI2: Security Profile
bug major open
#702: Normative text within security considerations
FAPI2: Security Profile
bug major open
#695: iat, nbf clause readability
FAPI2: Security Profile
bug major resolved
#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
#699: FAPI 2 vs. Security BCP Gap Analysis
FAPI2: Security Profile
bug major open
#697: FAPI2SP have links to https://openid.bitbucket.io/
FAPI2: Security Profile
bug major resolved
#692: CAA records
FAPI2: Security Profile
bug major resolved
#690: 5.1.1. Introduction recommends Grant Management but the maturity level of the document makes it inappropriate to recommend it in the FIANL specification
FAPI2: Security Profile
bug major open
#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
#638: Add some more text to Introduction
FAPI2: Security Profile
bug major resolved
#678: (ed) Privacy considerations is a top level clause while Security considerations is a second level subclause
FAPI2: Security Profile
bug major resolved
#646: NOTE in 5.2.1 has "can"
FAPI2: Security Profile
bug major resolved
#672: Inconsistent capitalization of "Client"
FAPI2: Security Profile
bug major resolved
  2. 1
  3. 2
  4. 3
  5. 4
  6. 5