CERN FTS pilot & tokens - progress

• Now configured also to support ATLAS token issuer
  • successful transfers test between dCache (PRAGUELCG2) <-> EOS (CERN) <-> StoRM (INFN-T1)
  • audience was not configured correctly on EOS ATLAS (already discussed with EOS Ops)
  • different StoRM behavior for "stat" operation
• StoRM: storage.modify doesn't allow stat operations while this is allowed in dCache & XRootD
  • preferred solution
    • storage.create & storage.modify should allow "stat" operation
    • StoRM code needs to be updated
  • currently FTS needs storage.read + storage.modify when StoRM is HTTP-TPC destination
    • releasing fixed StoRM & deploying at sites takes time and DC24 is already quite close
    • Rucio will be able to use workaround with read+modify for DC24 transfers
  • consistency of WLCG JWT profile implementation is certainly the important thing
    • posix filesystems also would typically not require r for w
    • requiring read for "stat" is a bit confusing

Operational model for tokens during DC24

• CERN would like to know rates, who will be included, what are our plans with token related mini-challenges
  • asked for a document that can be shared between iterested parties
  • would like to understand both ATLAS and CMS plans
• Rucio developers mentioned situation will be clear within two weeks once we have initial implementation for full chain with tokens
  • ATLAS and CMS behavior should be same by design (not much flexibility in Rucio token configuration in initial release that will be used in DC24)