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

Issues

Filter by:

Advanced search

Issues (101–125 of 539)

Title T P Status Votes Assignee Milestone Created Updated Actions
#603: Require servers to allow for clock skew
FAPI2: Security Profile
bug major resolved
#623: Replace reference to obsolete RFC7525 with BCP195
FAPI2: Security Profile
bug major resolved
#596: Non Repudiation
FAPI2: Message Signing
bug major resolved
#594: Value of JARM for non-repudiation
FAPI2: Message Signing
bug major resolved
#579: FAPI2SP: Note about client assertion audience looks misleading
FAPI2: Security Profile
bug major resolved
#597: Add text about conformance testing to FAPI2
FAPI2: Security Profile
bug major resolved
#629: FAPI2: Specify that redirect_uri's must be exact match
FAPI2: Security Profile
bug major resolved
#604: Please put "Draft" in the title of drafts
FAPI2: Security Profile
bug major resolved
#616: Add section about errata changes
FAPI 1: Advanced
bug major resolved
#624: " client's misconfigured token endpoint" is confusing
FAPI 1: Advanced
bug major resolved
#557: [FAPI 2.0] Move "MTLS Protection of all endpoints" from [Message Signing] to [Security Profile]
FAPI2: Security Profile
bug major resolved
#562: Scope needs clarification
FAPI2: Security Profile
bug major resolved
#627: Proposed change to invalid redirect url test in all FAPI conformance suites
FAPI 1: Advanced
bug major resolved
#609: CIBA - Make clear limitation of binding message
CIBA
bug major open
#628: Send acceptance of the report by U Stuttgart for WP2
task major resolved
#575: Issue with http sig request/response binding
FAPI2: Message Signing
bug major resolved
#608: Make clear that requests and responses to resource servers don't have to be bound
FAPI2: Message Signing
bug major resolved
#626: DPoP reference needs to be updated to the RFC
FAPI2: Security Profile
bug major resolved
#625: Changes to introduction of http signing section
FAPI2: Message Signing
bug major resolved
#600: Errata to remove "Financial-grade" references from FAPI1
FAPI 1: Advanced
bug major resolved
#549: Network Layer Protections restrict use of more recent TLS 1.2 ciphers
FAPI2: Security Profile
bug 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
#618: Certification/conformance: Strictness of checking error responses
bug major resolved
#495: Certification: Requirements for alg support in RPs/OPs
Certification
bug major resolved
  2. 1
  3. 2
  4. 3
  5. 4
  6. 5
  7. 6
  8. 7
  9. …
  10. 21
  11. 22