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

Issues

Filter by:

Advanced search

Issues (351–375 of 523)

Title T P Status Votes Assignee Milestone Created Updated Actions
#262: should long lived access tokens be permitted
FAPI 1: Baseline
enhancement major resolved
#207: RS256 vs PS256 (again)
FAPI 1: Advanced
bug major resolved
#251: refresh token expiry time
FAPI 1: Advanced
enhancement major resolved
#133: Two documents are labelled as part 3
Part 3: Open Data
bug major duplicate
#205: Add requirement for Client to verify state matches session
FAPI 1: Advanced
bug major resolved
#227: Add intro to FAPI RW - to explain that we don't support public clients
FAPI 1: Advanced
bug major resolved
#299: "In addition, the confidential client for write operations" causes confusion
FAPI 1: Advanced
bug major resolved
#203: Guidance around jwks and jwks_uri
FAPI 1: Advanced
bug major resolved
#277: FAPI-RW: Is disallowing signed id_tokens allowed? (i.e. always used signed+encrypted)
FAPI 1: Advanced
bug major resolved
#300: 5.2.3. Public client should be renamed to 5.2.3. Mobile client
FAPI 1: Advanced
bug major invalid
#301: 5.2.3. - 6 Is `amr` always required?
FAPI 1: Advanced
bug major invalid
#110: more definition of s_hash
FAPI 1: Advanced
bug major resolved
#274: Require HSTS for authorization server
FAPI 1: Advanced
bug major resolved
#180: Behaviour of AS when presented with a non-uuid x-fapi-interaction-id is not clearly defined
FAPI 1: Baseline
bug major resolved
#294: x-fapi-customer-ip-address should probably have an example for ipv6
FAPI 1: Baseline
bug major resolved
#270: JARM+FAPI-RW+openid client session binding
FAPI 1: Advanced
bug major resolved
#154: Behaviour of AS undefined if no acr claim supplied by client
FAPI 1: Advanced
bug major resolved
#247: Make JARM equal alternative
FAPI 1: Advanced
enhancement major resolved
#170: Remove Public Client Support
FAPI 1: Baseline
proposal major resolved
#281: update MTLS reference to point at RFC
FAPI 1: Advanced
bug major resolved
#175: Clarify attacker model (PKCE method and CSRF protection)
FAPI 1: Baseline
enhancement major resolved
#220: [BIS] Clarify attacker model (PKCE method and CSRF protection)
FAPI 1: Baseline
enhancement major resolved
#275: Adopt PAR & RAR as recommended way to convey authorization data
FAPI 1: Advanced
bug major resolved
#280: FAPI 2.0: Use ISO requirements conventions instead of IETF
Others
bug major resolved
#8: Should hard coded paths be avoided
Part 4: Protected Resources - RO
task major closed
  2. 1
  3. 2
  4. …
  5. 13
  6. 14
  7. 15
  8. 16
  9. 17
  10. 18
  11. 19
  12. 20
  13. 21