IAM is creating and storing refresh tokens, even though they are not returned to Rucio (GH issue)
We were asked to removed the offline_access scope from the token request.
But firtst, we must verify with FTS that their workflows will still continue to work, and devise an alternative method to communicate whether to assume the lifecycle of the token or not.
CMS
Issue with recreating rules:
Context: a rule that has already expired exists, and before the rule has been processed by the Cleaner, another request to create the rule happens
This is mostly in the context of a WFMS, though it might apply to individual users as well.
Can the expired_at be part of the unique constraint? To discuss in a GitHub issue.
Question about source selection strategies. To ask on Mattermost.
Fermilab
Adapting the policy packages to the latest upstream
RUBIN
Judge Injector takes too much time (25-35 minutes for ??K files)
The internal metrics suggest the delay may be in the apply_rule() function
Rucio permissions
Many are for just account=root and admin=True. Can they be simplified?
But also: to get a better overview fo what administrators versus regular users are allowed to do. To consider expanding the documentation.
DaFab
Demonstration of the new metadata mechanism at a workshop this winter
ESCAPE
Addressing issues with OIDC tokens
Fixed the token-exchange workflow with IAM.
Setting up the Rucio 34 Web UI
Preparing the deployment of Rucio 35
CERN IT
Setting up a pilot instance for the AMS experiment, late this year or early next year
PIC
Rucio instance for LST
Update from Rucio 32 to 35, plus additional configuration