-- Main.dimou - 15 Jun 2006

Why VOMRS on top of voms-admin

Information sent to the TCG (via M. Schulz) for discussion on 8 Jun 2006.

The following web links express what vomrs can do that voms-admin can't:

1. Iinterfacing to third party ID Provider (such as Fermilab LDAP CNAS, Cern Human Resources database etc)

1. Grid User Regristration and VO Management Requirements http://edms.cern.ch/document/428034 containing:

• periodic VO user expiration
• support for Institutional VO member expiration
• prompt to re-sign the Grid AUP and support of its versions
• provision for displaying the VO AUP and its versioning
• possibility to suspend users
• multiple certificates per user
• ability to request group/group role assignment
• description of the group/group roles, ability to link role to a particular group
• dynamic set of personal information per VO, private and public set of personal information
• event notification and ability to select set of subscribed events
• decreased load on VO Admin by introducing the hierarchy of administrators such as Representative, Group Managers etc

All the above, since we concluded in favour of vomrs from the very 1st 2004-06-14 LCG Registration Task Force meeting in http://dimou.web.cern.ch/dimou/lcg/registrar/TF/meetings/, (see minutes) were implemented following requirements by the VO Admins or the JSPG. Examples:

https://savannah.cern.ch/bugs/?func=detailitem&item_id=15164

https://savannah.cern.ch/search/?words=vomrs+groups+roles&type_of_search=bugs&Search=Search&exact=1#options