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

Issues

Filter by:

Advanced search

Issues (201–225 of 505)

Title T P Status Votes Assignee Milestone Created Updated Actions
#511: 2.4 The Processing rules by the client does not use normative language.
JARM
bug major resolved
#516: 2.4 bullet 5. just states "checks its signature"
JARM
bug major resolved
#510: Prohibition of alg=none not quite enough
JARM
bug major resolved
#517: 3. Client Metadata bullets formatting are hard to read
JARM
bug major resolved
#514: Five occurence of "this draft" need to be changed to "this document"
JARM
bug major resolved
#518: Move 6. Acknowledgement after IANA Consideration or Informative References
JARM
bug major resolved
#478: FAPI2 Baseline + jarm & iss draft
FAPI2: Security Profile
bug minor resolved
#496: clock sync and FAPI2 baseline
FAPI2: Security Profile
bug major resolved
#436: Change grant_management_action "update" to "add" or "append"
Grant Management
proposal major resolved
#336: FAPI 2 Baseline - Client types
FAPI2: Security Profile
proposal minor resolved
#480: FAPI 2 Baseline: shall support authorization details if scope is not expressive enough needs enhancement to cover standard oidc claims.
FAPI2: Advanced Authorization
bug minor resolved
#499: Re structure FAPI2 baseline
FAPI2: Security Profile
bug major resolved
#501: Clarify that authorization response encryption is not required for FAPI2 + Message signing / JARM
FAPI2: Message Signing
enhancement minor resolved
#498: Rename "FAPI2: Advanced Authorization"
FAPI2: Advanced Authorization
bug major resolved
#500: Signal that FAPI2 can work with client credentials grant
FAPI2: Security Profile
bug major resolved
#401: Use of the phrase "non-repudiation"
FAPI2: Message Signing
bug major resolved
#491: Link attacker model to FAPI 2 Advanced
FAPI2: Message Signing
bug major resolved
#477: FAPI2 + dpop nonces
FAPI2: Security Profile
bug major resolved
#497: RS Clauses re access token
FAPI2: Security Profile
bug major resolved
#493: certification query: supply of TLS client certs & use of mtls_endpoint_aliases
FAPI2: Message Signing
bug major resolved
#430: Add "Scope" clause to FAPI 2.0
FAPI2: Security Profile
bug major resolved
#492: EdDSA in FAPI 2.0
FAPI2: Security Profile
proposal minor resolved
#464: Review casing of keywords
Grant Management
task major resolved
#459: Should JARM be mandated for code flow with PAR and PKCE?
FAPI 1: Advanced
bug major resolved
#269: JARM response contents clarifications
JARM
bug major resolved
  2. 1
  3. 2
  4. …
  5. 7
  6. 8
  7. 9
  8. 10
  9. 11
  10. 12
  11. …
  12. 20
  13. 21