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
#687: FAPI-CIBA shall be inheriting these sections from a chosen security profile (FAPI 1 or FAPI 2)?
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
#660: Define requirements for OpenAPI FAPI securityScheme type
Others
proposal major open 2
#630: Android Carrier OpenID API
Others
proposal major open
#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
#602: "Client" is misleading in the context of signed introspection responses
FAPI2: Message Signing
proposal major resolved
#599: FAPI Acronym
proposal major open
#570: Deprecation & removal of FAPI 1 Implementer's Draft conformance certification tests/programme
FAPI 1: Advanced
proposal major closed
#552: Adapt FAPI-CIBA to be used with FAPI 1 and FAPI2
CIBA
proposal major resolved
#529: Applicability of Security BCP to FAPI 2.0
FAPI2: Security Profile
proposal minor resolved
#523: Rotation of Refresh token - Compromised client highlighted by AU - CDR Independent review.
FAPI2: Security Profile
proposal critical resolved
#492: EdDSA in FAPI 2.0
FAPI2: Security Profile
proposal minor resolved
#479: Change to the naming of FAPI
Others
proposal major resolved
#469: Add protocol version and variant identifier
FAPI2: DCR & DCM
proposal minor open 1
#467: Can FAPI specs support ecosystems where smart phones aren't common, e.g. by using USSD
Others
proposal minor resolved
#466: Proposal for FAPI DCR/DCM (Dynamic Client Registration/Management) profile
FAPI2: DCR & DCM
proposal major open
#456: Proposal - should we remove support for refresh token rotation from FAPI 2.0 (one of the drafts)
FAPI2: Security Profile
proposal minor resolved
#439: Grant Management API Query Response expiration and issued at
Grant Management
proposal major resolved
#437: Grant Management API Query Response missing normative structure
Grant Management
proposal major resolved
#436: Change grant_management_action "update" to "add" or "append"
Grant Management
proposal major resolved
#432: FAPI2 Trust Framework structure
Others
proposal major open
#424: Digest vs. Content-Digest
HTTP Signing
proposal minor resolved
#423: Refresh token used as bearer token for Grant Management APIs
Grant Management
proposal minor resolved
  2. 1
  3. 2
  4. 3
  5. 4