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

Issues

Filter by:

Advanced search

Issues (1–25 of 355)

Title T P Status Votes Assignee Milestone Created Updated Actions
#673: Additional author(s) for FAPI2
FAPI2: Security Profile
bug major resolved 3
#155: Support authorization and identity federation use cases for the same client_id
FAPI 1: Advanced
proposal major resolved 2
#674: length of nonce tested in OP conformance tests
FAPI2: Security Profile
bug major resolved 1
#403: proposed new FAPI certification test: private_key_jwt client authentication assertion where aud contains multiple values
FAPI 1: Advanced
proposal major resolved 1
#398: new certification check: aud in client assertions is issuer
FAPI 1: Advanced
bug major resolved 1
#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
#379: lifetime of grant_id
Grant Management
bug major resolved 1
#442: Grant vs Consent confusion
Grant Management
enhancement major resolved 1
#199: CIBA - which modes to support
CIBA
bug major resolved 1
#658: allow use of a future fully specified JWS algorithm identifier for EdDSA w/ Ed25519
FAPI2: Security Profile
enhancement major resolved
#670: Use of FAPI with mandatory MTLS
FAPI2: Security Profile
bug major resolved
#651: Avoid "should be" and "shall be" where possible
FAPI2: Security Profile
bug major resolved
#679: (ed) replace (this) specification with (this) document
FAPI2: Security Profile
bug major resolved
#642: Continuation of #619 -- Add some text to make the readers aware of the caveats.
FAPI2: Security Profile
bug major resolved
#550: Should Network Layer Protections be made server-side enforced?
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
#638: Add some more text to Introduction
FAPI2: Security Profile
bug major resolved
#678: (ed) Privacy considerations is a top level clause while Security considerations is a second level subclause
FAPI2: Security Profile
bug major resolved
#646: NOTE in 5.2.1 has "can"
FAPI2: Security Profile
bug major resolved
#672: Inconsistent capitalization of "Client"
FAPI2: Security Profile
bug major resolved
#665: Reference PAR in 5.3.1.1 (12)
FAPI2: Security Profile
bug major resolved
#659: No normative statement on id_token encryption
FAPI2: Security Profile
bug major resolved
#671: Attacker model: Renumber attackers, reference formal analysis
FAPI2: Attacker Model
bug major resolved
#641: Scope states "stated attacker model" without explicitly referencing it
FAPI2: Security Profile
bug major resolved
  2. 1
  3. 2
  4. 3
  5. 4
  6. 5
  7. 6
  8. …
  9. 14
  10. 15