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

Issues

Filter by:

Advanced search

Issues (76–100 of 128)

Title T P Status Votes Assignee Milestone Created Updated Actions
#281: update MTLS reference to point at RFC
FAPI 1: Advanced
bug major resolved
#163: more description of the security model
FAPI 1: Advanced
bug minor resolved
#275: Adopt PAR & RAR as recommended way to convey authorization data
FAPI 1: Advanced
bug major resolved
#278: duplicate kids in authorization server's jwks
FAPI 1: Advanced
bug major duplicate
#184: Privacy implications of oauth-mtls due to tls 1.2 sending client certs unencrypted
FAPI 1: Advanced
bug major closed
#158: FAPI part 2 - request object for public clients (signing key?)
FAPI 1: Advanced
bug major resolved
#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
#208: Part 2 should limit allowed JWE algorithms
FAPI 1: Advanced
bug major closed 1
#167: (ed) 5.2.3 - Last Para should be a numbered bullet
FAPI 1: Advanced
bug major resolved
#149: Make it clear that the entire flow is OIDC Hybrid Flow (related to #155)
FAPI 1: Advanced
bug major resolved
#221: FAPI-RW ID2 needs some further tweaks for JARM
FAPI 1: Advanced
bug major resolved
#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
#178: Editorial: Specs should explain the risks of writing an RP library from scratch
FAPI 1: Advanced
bug major closed
#145: Consider mobile app <-> mobile app authentication flows
FAPI 1: Advanced
bug major resolved
#144: Apply the new name to the Part 1 and 2
FAPI 1: Advanced
bug blocker resolved
#159: FAPI part 2 - JWE encrypted ID Tokens
FAPI 1: Advanced
bug minor resolved
  2. 1
  3. 2
  4. 3
  5. 4
  6. 5
  7. 6