VOMS Admin server v. 3.3.3

This release

  • fixes a problem that caused the removal of all pending requests if a user was removed from the VOMS database
  • fixes a problem in the handling of multiple VO membership requests
  • introduces the voms.request.vo_membership.require_group_manager_selection configuration flag to enable/disable the mandatory selection of a group manager (GM) by applicants at VO registration time. By default, GM selection is mandatory.

Bug fixes and improvements

  • VOMS-609 : Removing a user causes the removal of all pending requests
  • VOMS-608 : VOMS Admin does not handle correctly multiple VO membership request
  • VOMS-607 : Mandatory Group manager selection should be configurable
  • VOMS-606 : VOMS should refer to Institute.name instead of Institute.originalName when populating institution field from the CERN HR DB

Installation and configuration

Clean install

Follow the instructions in the VOMS System Administrator Guide.

Upgrade from v. >= 3.2.0

The upgrade requires a service restart. After the packages have been updated, run the following commands:

service voms-admin stop
service voms-admin undeploy
service voms-admin start

Upgrade from earlier VOMS Admin versions

Upgrading to this version requires an upgrade of the database and a reconfiguration depending on the version of VOMS admin which is being upgraded. Follow the instructions in the VOMS System Administrator Guide.

Upgrade from Actions required
v. 3.1.0 db upgrade
v. 2.7.0 db upgrade reconfiguration