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

Issues

Filter by:

Advanced search

Issues (526–550 of 685)

Title T P Status Votes Assignee Milestone Created Updated Actions
#15: Client Authentication, not Client Authorization
FAPI 1: Baseline
bug minor resolved
#37: Fix security consideration text
FAPI 1: Baseline
bug major resolved
#33: John's Security Section Review Result
Part 4: Protected Resources - RO
bug major resolved
#30: 5.2 - ed - 5.2 has a hanging paragraph
FAPI 1: Baseline
bug minor resolved
#23: How do I find AccountID to use in transfer?
Part 4: Protected Resources - RO
task major resolved
#25: ASK: Adopt Editors-Draft-00 as the new Working Draft
Part 4: Protected Resources - RO
proposal major resolved
#16: Client Authentication -- Do we need TLS mutual authentication?
FAPI 1: Baseline
proposal major resolved
#306: Webhook Support in FAPI
Implementation & Deployment Advice
proposal major open
#2: Accounts: Total Pages and Page does not make sense
Part 4: Protected Resources - RO
bug major wontfix
#7: Add "Open Data" data set
Part 3: Open Data
bug major wontfix
#20: Meaning of the Surrogate Identifier Clause not clear
Part 4: Protected Resources - RO
bug major wontfix
#22: Undefined OAuth response parameter "user_id" appears in the text
FAPI 1: Baseline
bug major closed
#17: Incomplete sentence "In line with FFIEC (Federal Financial Institutions Examination Council) guidance on Authentication to mitigate security risks."
FAPI 1: Baseline
bug major resolved
#622: Review FAPI1 security considerations for clarity
FAPI 1: Advanced
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
#695: iat, nbf clause readability
FAPI2: Security Profile
bug major new
#693: MTLS section readability
FAPI2: Security Profile
bug major open
#674: length of nonce tested in OP conformance tests
FAPI2: Security Profile
bug major resolved 1
#651: Avoid "should be" and "shall be" where possible
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
#432: FAPI2 Trust Framework structure
Others
proposal major open
#675: update refs for HTTP Message Signatures & Digest Fields
FAPI2: Message Signing
task minor open
#659: No normative statement on id_token encryption
FAPI2: Security Profile
bug major resolved
#521: Change name and file name of FAPI 2 Advanced to FAPI 2 Message Signing
FAPI2: Message Signing
bug major resolved
#577: FAPI2SP appears to permit response_types "id_token", "id_token token" and "none"
FAPI2: Security Profile
bug minor resolved
  2. 1
  3. 2
  4. …
  5. 20
  6. 21
  7. 22
  8. 23
  9. 24
  10. 25
  11. 26
  12. 27
  13. 28