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

Issues

Filter by:

Advanced search

Issues (1–13 of 13)

Title T P Status Votes Assignee Milestone Created Updated Actions
#185: PKCE or Part2 mechanisms?
FAPI 1: Baseline
bug major closed
#196: OAuth Security BCP and FAPI
FAPI 1: Baseline
bug major closed
#86: The read only spec should not contain 'if possible' in section 5.2.2
FAPI 1: Baseline
enhancement major closed
#187: Part 1 client requirements for state/nonce aren't reflected as authorization server requirements
FAPI 1: Baseline
bug major closed
#213: requirements on RSA/EC key sizes should apply to more situations
FAPI 1: Baseline
bug major closed
#11: OAuth Profile should mandate RFC7636 (PKCE) for code flow
FAPI 1: Baseline
proposal major closed 1
#5: Create Read Only Security Profile
FAPI 1: Baseline
task major closed
#21: Residual Data clause should be generalized and moved to privacy considerations
FAPI 1: Baseline
bug major closed
#22: Undefined OAuth response parameter "user_id" appears in the text
FAPI 1: Baseline
bug major closed
#84: RFC2616 is obsolete and references to it should be replaced with updated RFCs
FAPI 1: Baseline
bug major closed
#79: Part 1: issues with x-fapi-customer-last-logged-time header
FAPI 1: Baseline
bug major closed
#63: There is no qualification on x-fapi-customer-id
FAPI 1: Baseline
bug major closed
#69: Notes like this are strange “NOTE: Providing access to Javascript clients or not has different security properites.;”
FAPI 1: Baseline
bug major closed