Project

General

Profile

Feature #5812

Support authentication configuration against Non fermilab VOMS

Added by Parag Mhashilkar over 5 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
04/02/2014
Due date:
% Done:

100%

Estimated time:
Stakeholders:

RunII, LBNE

Duration:

Description

Current of jobsub server and the auth module assumes the Fermilab VO membership. LBNE, Dzero and CDF have there own voms. We need to extend the support to other VOMS. This should be driven through configuration


Related issues

Has duplicate JobSub - Bug #5793: proxies for lbne not being created correctlyClosed2014-04-01

History

#1 Updated by Parag Mhashilkar over 5 years ago

  • Target version changed from v0.3 to v0.2.1

#2 Updated by Parag Mhashilkar over 5 years ago

  • Status changed from New to Feedback
  • Assignee changed from Parag Mhashilkar to Dennis Box
  • Stakeholders updated (diff)

Dennis, I have merged the changes to master and did some testing against groups nova and dzero. Can you please merge it to your working branches so this gets tested more rigorously? For an acctgroup with a different voms server, you need to add it to the respect group. Following is the example for dzero VO. If no voms attribute is specified in the ini file, it defaults to the old behavior, i.e. use fermilab voms

[d0]
GROUP = d0
STORAGE_GROUP = d0
CONDOR_TMP = /d0/data/condor-tmp/${LOGNAME}
CONDOR_EXEC = /d0/app/condor-exec/${LOGNAME}
voms = dzero:/dzero/users

#3 Updated by Dennis Box over 5 years ago

  • Status changed from Feedback to Closed

tested, the test suite handles this by setting GROUP to some accounting group with a different voms. Need to document the voms setting in jobsub.ini

#4 Updated by Parag Mhashilkar over 5 years ago

  • % Done changed from 0 to 100


Also available in: Atom PDF