Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow VO-agnostic proxy certificate production #220

Open
Soap2G opened this issue Feb 3, 2025 · 0 comments · May be fixed by #224
Open

Allow VO-agnostic proxy certificate production #220

Soap2G opened this issue Feb 3, 2025 · 0 comments · May be fixed by #224
Assignees

Comments

@Soap2G
Copy link

Soap2G commented Feb 3, 2025

Communities that need to have a ftsRenewal daemon that creates proxies that are not registered in a VO (i.e. do voms-proxy-init without the --voms option, which is identical to grid-proxy-init), cannot do it.
Reasons are:

  1. The default values in the chart are related to CMS
  2. In order to declare RUCIO_FTS_VOMS in the the fts cronjob, we check for vo, so in general we always find something.
  3. This means that when doing voms-proxy-init the variable RUCIO_FTS_VOMS always exists.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

Successfully merging a pull request may close this issue.

1 participant