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

Issues

Filter by:

Advanced search

Issues (1–25 of 82)

Title T P Status Votes Assignee Milestone Created Updated Actions
#570: Deprecation & removal of FAPI 1 Implementer's Draft conformance certification tests/programme
FAPI 1: Advanced
proposal major closed
#244: FAPI-CIBA: Does "JWS/JWE Algorithm considerations" apply to Read-Only, too?
CIBA
proposal major closed
#124: More examples as an appendix
FAPI 1: Advanced
proposal major closed
#94: Consider solutions to developing economies using stored value
Others
proposal major closed
#95: KYC sharing with user consent based on Modrna
Others
proposal major closed
#225: Remove references to OAuth Token Binding
FAPI 1: Advanced
proposal major closed
#201: CIBA: acr/amr alignment
CIBA
proposal major closed
#121: CIBA: Binding Messages
CIBA
proposal minor closed
#174: CIBA: End-user Identifiers
CIBA
proposal major closed
#193: Part 2, Section 5.2.2.: remove response type "code id_token token"
FAPI 1: Advanced
proposal major closed
#11: OAuth Profile should mandate RFC7636 (PKCE) for code flow
FAPI 1: Baseline
proposal major closed 1
#51: Message source authentication failure -
FAPI 1: Baseline
proposal minor closed
#109: is s_hash necessary?
FAPI 1: Advanced
proposal major closed
#72: Spec not clear as to which auth flows are supported
FAPI 1: Advanced
proposal major closed
#28: International names for retirement savings account names
Part 4: Protected Resources - RO
proposal minor wontfix
#682: Clarify allowed use of `state` and required CSRF protection in FAPI 2.0 SP
FAPI2: Security Profile
proposal major resolved
#602: "Client" is misleading in the context of signed introspection responses
FAPI2: Message Signing
proposal major resolved
#617: Security issue in the JWT Response for OAuth Token Introspection specification
FAPI2: Message Signing
proposal major resolved
#403: proposed new FAPI certification test: private_key_jwt client authentication assertion where aud contains multiple values
FAPI 1: Advanced
proposal major resolved 1
#467: Can FAPI specs support ecosystems where smart phones aren't common, e.g. by using USSD
Others
proposal minor resolved
#424: Digest vs. Content-Digest
HTTP Signing
proposal minor resolved
#353: FAPI for Berlin Group openFinance Framework
Others
proposal major resolved 1
#253: Pushed Request Object - Signed request object shouldn't be used for client authentication
Pushed Request Uri
proposal major resolved 1
#245: FAPI-CIBA: Client Authentication at Backchannel Authentication Endpoint
CIBA
proposal minor resolved
#216: TLS_ECDHE_ECDSA cipher suites
FAPI 1: Advanced
proposal major resolved
  2. 1
  3. 2
  4. 3
  5. 4