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
#688: Simplifying the usage of FAPI-CIBA and FAPI 2 profiles together
CIBA
proposal major new
#682: Clarify allowed use of `state` and required CSRF protection in FAPI 2.0 SP
FAPI2: Security Profile
proposal major resolved
#687: FAPI-CIBA shall be inheriting these sections from a chosen security profile (FAPI 1 or FAPI 2)?
CIBA
proposal major new
#660: Define requirements for OpenAPI FAPI securityScheme type
Others
proposal major open 2
#630: Android Carrier OpenID API
Others
proposal major open
#432: FAPI2 Trust Framework structure
Others
proposal major open
#570: Deprecation & removal of FAPI 1 Implementer's Draft conformance certification tests/programme
FAPI 1: Advanced
proposal major closed
#469: Add protocol version and variant identifier
FAPI2: DCR & DCM
proposal minor open 1
#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
#607: Create a Resource Server Profile on top of FAPI 2
Implementation & Deployment Advice
proposal minor open
#466: Proposal for FAPI DCR/DCM (Dynamic Client Registration/Management) profile
FAPI2: DCR & DCM
proposal major open
#599: FAPI Acronym
proposal major open
#295: Possible support for "embedded" SCA mode
Others
proposal major new
#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
#306: Webhook Support in FAPI
Implementation & Deployment Advice
proposal major open
#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
#254: Pushed Request Object - The payload of the response
Pushed Request Uri
proposal major resolved
#244: FAPI-CIBA: Does "JWS/JWE Algorithm considerations" apply to Read-Only, too?
CIBA
proposal major closed
#362: Language to use on the certification pages for ID2 vs Final
Certification
proposal major resolved
  2. 1
  3. 2
  4. 3
  5. 4