WLCG-AuthZ-WG/common-jwt-profile

Issues

• Inconsistency in token issuer public key cache lifetimes

  #52 opened 3 months ago
  1

• distinguish creation of directories vs. files

  #50 opened 3 months ago
  0

• Investigate convergence with AARC representation of groups

  #44 opened a year ago
  1

• Unclear how to handle backwards-compatible changes

  #43 opened a year ago
  10

• Unclear semantics of top-level group's name

  #39 opened a year ago
  1

• Document doesn't define what is a virtual organisation

  #38 opened 3 months ago
  2

• Is overriding POSIX required behaviour?

  #37 opened a year ago
  0

• Missing description for listing directories

  #36 opened a year ago
  1

• `storage.create` includes protocol-specific behaviour

  #35 opened 3 months ago
  10

• No discussion on how to map the scope path to request path

  #34 opened a year ago
  0

• Poorly specified renaming/moving authorisation

  #33 opened a year ago
  5

• Poor specified of storage `$PATH` type

  #32 opened 3 months ago
  2

• Bad example for storage scope-based authorisation statements

  #31 opened 6 months ago
  3

• Documenting a third approach to authorisation

  #30 opened a year ago
  0

• Identifying VO membership from the issuer

  #29 opened a year ago
  3

• Document does not stated clearly that an issuer supports a single VO

  #28 opened a year ago
  9

• Scope of storage capabilities is ambiguous for SEs with tape storage

  #26 opened a year ago
  6

• Use RFC 9068 for token version

  #25 opened a year ago
  4

• Submitting pilots to computing resources: `wlcg.groups` claim and `client_credentials` flow

  #24 opened a year ago
  22

• Limitation of the storage claim

  #22 opened 2 years ago
  20

• Improve `storage.*:/path` description

  #21 opened 3 months ago
  6

• Guidance on Refresh Token Rotation

  #18 opened 2 years ago
  2

• Use Case: Multiple VOs supported by a "common implementation"

  #9 opened 2 years ago
  19

• Update document to RFC token exchange

  #8 opened 3 years ago
  0