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

Issues

Filter by:

Advanced search

Issues (1–25 of 177)

Title T P Status Votes Assignee Milestone Created Updated Actions
#570: Deprecation & removal of FAPI 1 Implementer's Draft conformance certification tests/programme
FAPI 1: Advanced
proposal major closed
#394: Old links to part 1 / part 2 in git repo no longer work
FAPI 1: Advanced
bug major closed
#367: missing and extra "ands"
FAPI 1: Advanced
bug minor closed
#325: Editorial: TLS 8.5 BCP195 not referenced in bibliography.
FAPI 1: Advanced
enhancement trivial closed
#124: More examples as an appendix
FAPI 1: Advanced
proposal major closed
#304: Are duplicates of the response_type, and scope values necessary when using PAR?
FAPI 1: Advanced
bug major closed
#307: FAPI-RW: Require pkce when using PAR
FAPI 1: Advanced
bug major closed
#264: expand on privacy considerations for id_tokens returned in front channel
FAPI 1: Advanced
enhancement major closed
#166: (ed) Need to add JARM in the introductions
FAPI 1: Advanced
bug major closed
#181: Userinfo response should be a jwt. OP's should support UserInfo JWT response
FAPI 1: Advanced
enhancement minor closed
#184: Privacy implications of oauth-mtls due to tls 1.2 sending client certs unencrypted
FAPI 1: Advanced
bug major closed
#250: certification clarification request: grant_types_supported in discovery
FAPI 1: Advanced
bug major closed
#263: Are scopes required to be returned when exchanging Refresh Tokens for Access Tokens.
FAPI 1: Advanced
bug major closed
#261: Part 1/2: client authentication requirements apply to all endpoints client authentication is used at
FAPI 1: Advanced
bug major closed
#248: Part 2 text prevents the use of TLS 1.3
FAPI 1: Advanced
bug major closed
#218: LoA3 requirement in part2 may be too much
FAPI 1: Advanced
bug major closed
#177: request object should contain iat or nbf
FAPI 1: Advanced
bug major closed
#225: Remove references to OAuth Token Binding
FAPI 1: Advanced
proposal major closed
#208: Part 2 should limit allowed JWE algorithms
FAPI 1: Advanced
bug major closed 1
#214: restricting 'aud' in request object to a single value
FAPI 1: Advanced
bug major closed
#190: aud should be mandatory in requests objects
FAPI 1: Advanced
bug major closed
#211: clients should be required to send a 'reasonable' exp in request object
FAPI 1: Advanced
bug major closed
#189: behaviour of AS when client passes different values in request object vs OAuth 2.0 request syntax
FAPI 1: Advanced
bug major closed
#217: "shall additionally send duplicates of the parameters/values using the OAuth 2.0 request syntax where required by the OAuth specification" is vague
FAPI 1: Advanced
bug major closed
#193: Part 2, Section 5.2.2.: remove response type "code id_token token"
FAPI 1: Advanced
proposal major closed
  2. 1
  3. 2
  4. 3
  5. 4
  6. 5
  7. 6
  8. 7
  9. 8