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

Issues

Filter by:

Advanced search

Issues (101–125 of 140)

Title T P Status Votes Assignee Milestone Created Updated Actions
#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
#142: Standardising ‘lodging intent”
FAPI 1: Advanced
proposal major resolved
#193: Part 2, Section 5.2.2.: remove response type "code id_token token"
FAPI 1: Advanced
proposal 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
#155: Support authorization and identity federation use cases for the same client_id
FAPI 1: Advanced
proposal major resolved 2
#152: request objects should have iat and exp
FAPI 1: Advanced
bug major resolved
#162: does part 2 allow client_secret_jwt?
FAPI 1: Advanced
bug major resolved
#157: FAPI part 2 - public clients and mTLS
FAPI 1: Advanced
enhancement major resolved
#150: Mandate at_hash check in the ID Token from the token endpoint
FAPI 1: Advanced
bug major closed
#143: Guidance required for decoupled
FAPI 1: Advanced
bug major closed
#141: Remove x-fapi-financial-id
FAPI 1: Advanced
bug major closed
#134: Should we define a discovery metadata for request object endpoint
FAPI 1: Advanced
bug major resolved
#136: responsibility
FAPI 1: Advanced
bug major closed
#137: Eliminate use of public clients
FAPI 1: Advanced
bug major closed
#130: we could be clearer about which id_token s_hash is required in
FAPI 1: Advanced
bug major resolved
#109: is s_hash necessary?
FAPI 1: Advanced
proposal major closed
#125: Create a FAPI WG response to the Berlin Group Consultation
FAPI 1: Advanced
task major resolved
#123: Is it okay for request object URNs to be predictable?
FAPI 1: Advanced
bug major closed
#112: Inconsistency around encrypted ID Tokens
FAPI 1: Advanced
bug major resolved
#111: MTLS only for Protected resources provisions?
FAPI 1: Advanced
bug major resolved
  2. 1
  3. 2
  4. 3
  5. 4
  6. 5
  7. 6