gLite VOMS Server and Administration Tools (MySQL)

1. Release Description

This release contains the MySQL version of the gLite VOMS Server and Administration Tools module v. 2.1.0. The following sections provide additional information about the release content, the module dependencies, the know bugs and issues and a list of bugs closed since the previous release. For information about installing and using the gLite VOMS Server and Administration Tools, please refer to the gLite Installation and User Guides.

This deployment module replaces the deployment module glite-voms-server.

2. Changes in this Release

2.1. Changes in functionality

2.1.1. VOMS-ADMIN

Installation changes:

There is now full support for using Oracle as the VOMS admin database backend. There are six new options to voms-admin-configure for configuring VOMS to use a preconfigured database account (see help for details)
This release continues to support the old "--dbapwd" database setup parameters that were offered in previous releases; however, this obsolete interface may disappear in a future VOMS Admin release.
The --copy-vomsd option to voms-admin-configure is not supported in this release.
Both MySQL and Oracle may be installed on a remote server; voms-admin-configure has been fixed to make sure that deployment suceeds and both VOMS services are configured correctly in this case.
The voms-admin-configure script now configures the VOMS core service with suitable default values for the --timeout, --loglevel and --logtype parameters.

Service changes:

By default, clients from localhost do not bypass the ACL checks any more. Please adapt your remaining local batch processes to use an authenticated connection using the host certificate. You can set the "voms.localhost.has.bypass" parameter to true to restore the former behaviour.
The VOMSAdmin.getVOName SOAP method is now publicly available for every client. No authorization checks are made. In previous releases, the client was expected to have the LIST privilege on the VO group to get the VO name.
You can now disable some or all parts of the web interface by editing voms.service.properties. For example, it is useful to disable the request interface when users are registered outside of VOMS Admin, e.g. with VOMRS. See voms-admin release notes for details.

· The new 'voms.readonly' option allows you to set up a read-only VOMS Admin server, in which all update operations are denied.

· The request scheduler is now enabled by default. This means that old requests are now deleted from the database by a periodically running background thread. Expired requests and requests which are explicitly deleted on the web interface are _completely_removed_ from the database after a short delay. See voms-admin release notes for details.

· The three database connection pools (for Updates, Queries and DirectUpdates) have been consolidated into a single pool to reflect that the suggested deployment method has been changed to use a single database account. The database connection handling layer has been rewritten accordingly.

· The list of known CAs is now always kept in memory. This greatly reduces (in some cases, halves) the number of SQL queries necessary for most SOAP operations.

· The overall performance of the service has been radically improved by limited caching of queried data across transactions. See voms-admin release notes for details.

· The performance of the ACL checking module has been greatly enhanced in the common case when there is no deny rule and so we can shortcut on the first allow rule found. See voms-admin release notes for details.

Web interface changes:

· The HTML VO welcome page at https://server:8443/voms/VONAME/ is now generated dynamically. It shows the VO name and your login information.

· You can now remove users from groups or roles using the web interface. The previous release removed users from the VO instead by mistake.

· The included ".pp" content files have been reorganized to follow the URLs that are currently used by the service. This means that there is again a default boilerplate text on the request submission page, and other pages.

Database changes

· The service is now fully capable of running on an Oracle database.

2.1.2. VOMS changes

· Removal of separate c-api

· Using of MySQL c api instead of mysql++

· Changes of error messages and logging system

2.2. Changes in Configuration

The configuration of the module has changed. Please update your configuration if you upgrade from a previous version of the VOMS server.

2.2.1. New configuration parameters

The following configuration parameters have been added:

File: glite-voms-server.cfg.xml

Parameter

Default value

Description

User-defined Parameters

voms.db.host

Hostname of the database server. Put 'localhost' if you run the database on the same machine. This parameter can be specified also separately per VO.

Example: localhost

[Type: 'string']

voms.admin.smtp.
host

Host to which voms-admin-service-generated emails should be submitted. Use 'localhost' if you have a fully configured SMTP server running on this host. Otherwise specify the hostname of a working SMTP submission service. This parameter can be specified also separately per VO. Example: localhost

[Type: 'string']

voms.mysql.admin.
password

Administrator login password for the MySQL database. This parameter can be specified also separately per VO.

Example: 'verySecret'

[Type: 'string']

Advanced Parameters

rgma.servicetool.
activate

true

Turn on/off servicetool for the node.

Example: true

[Type: 'boolean']

voms.mysql.admin.
name

root

Administrator login name for the MySQL database. This parameter can be specified also separately per VO.

Example: 'root'

[Type: 'string']

voms.db.mysql.port

3306

Port number of the database server for mysql. This parameter can be specified also separately per VO. Example: 3306

[Type: 'integer']

voms.db.oracle.port

1521

Port number of the database server for oracle. This parameter can be specified also separately per VO.

Example: 1521

[Type: 'integer']

System Parameters

voms.db.oracle.library

${GLITE_LOCATION}/lib/libvomsoracle.so

Location of the oracle voms libraries.

Example: ${GLITE_LOCATION}/lib/libvomsoracle.so

[Type: 'string']

VO Instances parameters

voms.db.name

Database name to be used to store VOMS information.

If you are upgrading from a release before 1.4, the default value up to release 1.3 was voms_${voms.vo.name}.

Example: VOMS_EGEE

[Type: 'string']

voms.db.user.name

Name of database user. This parameter can be specified also separately per VO. If you are upgrading from a release before 1.4, the default value up to release 1.3 was vo_adm.

Example: voUser

[Type: 'string']

voms.db.user.password

Password of database user defined in 'voms.db.user.name'. This parameter can be specified also separately per VO. If you are upgrading from a release before 1.4, the default value up to release 1.3 was the mysql root password.

Example: verySecret

[Type: 'string']

VOMS admin specific parameters

If you have decided not to run the voms-admin by setting 'voms.admin.install' to false you can leave these parameters empty or remove them.

voms.admin.
notification.e-mail

E-mail address that is used to send notification mails from the VOMS-admin.

Example: name.surname@domain.org

[Type: 'string']"

voms.admin.
certificate

The certificate file (in pem format) of an initial VO administrator. The VO will be set up so that this user has full VO administration privileges. Remove parameter or leave parameter empty if you don't want to create an initial VO administrator.

Example: '/your/path/admincert.pem'

[Type: 'string']

2.2.2. Removed configuration parameters

The following configuration parameters have been removed:

File: glite-voms-server.cfg.xml
Parameter	Comment
User defined parameters
vo.admin.e-mail	Replaced by parameter ‘voms.admin. notification.e-mail’.
voms.mysql.passwd	Replaced by parameter ‘voms.mysql.admin. password’
Advanced parameters
vo.ca.URI	Not used anymore.
System parameters
voms-admin.install	Replaced by parameter ‘voms.admin.install’ (now advanced parameter)

2.2.3. Changed configuration parameters

The following parameters have changed:

File: glite-voms-server.cfg.xml
Parameter	Default value	Description	Changes in parameter
Advanced Parameters
voms.db.type		Database type to be used. Can be 'mysql\|oracle'. This parameter cannot be specified separately per VO. Example: mysql [Type: 'string']	· The parameter has been moved from advanced to user defined. · The parameter has no default value any more.

2.3. Bug FIXES

This release introduces a set of bug fixes (for the full list of fixed bug see sections 5.2and 5.3)

3. Release contents

3.1. Glite sub-deployment modules

The gLite VOMS Server (MySQL) module installs/uses the following set of gLite deployment modules:

glite-voms-server-mysql
glite-rgma-servicetool
glite-security-utils

Please see the corresponding release notes of these modules for details.

3.2. Glite RPMS

The gLite VOMS Server MySQL module is composed of the following gLite components (list includes the gLite components of the other used gLite deployment modules listed in section 3.1):

Component name	Description	Version	File
glite-config	gLite configuration scripts	1.4.2	../../../../../../../glite-web/egee/packages/R1.4/R20050916/bin/rhel30/noarch/RPMS/glite-config-1.4.2-1.noarch.rpm
glite-rgma-api-java	Java API for R-GMA	4.1.5	../../../../../../../glite-web/egee/packages/R1.4/R20050916/bin/rhel30/noarch/RPMS/glite-rgma-api-java-4.1.5-1.noarch.rpm
glite-rgma-base	R-GMA basic configuration and documentation	4.1.19	../../../../../../../glite-web/egee/packages/R1.4/R20050916/bin/rhel30/noarch/RPMS/glite-rgma-base-4.1.19-1.noarch.rpm
glite-rgma-common-config	gLite rgma common configuration items installation	5.0.0	../../../../../../../glite-web/egee/packages/R1.4/R20050916/bin/rhel30/noarch/RPMS/glite-rgma-common-config-5.0.0-1.noarch.rpm
glite-rgma-servicetool	R-GMA service tool	4.1.19	../../../../../../../glite-web/egee/packages/R1.4/R20050916/bin/rhel30/noarch/RPMS/glite-rgma-servicetool-4.1.19-3.noarch.rpm
glite-rgma-servicetool-config	gLite R-GMA servicetool installation	5.1.0	../../../../../../../glite-web/egee/packages/R1.4/R20050916/bin/rhel30/noarch/RPMS/glite-rgma-servicetool-config-5.1.0-1.noarch.rpm
glite-rgma-stubs-servlet-java	Java client implementation stubs for R-GMA	4.1.13	../../../../../../../glite-web/egee/packages/R1.4/R20050916/bin/rhel30/noarch/RPMS/glite-rgma-stubs-servlet-java-4.1.13-1.noarch.rpm
glite-security-trustmanager	The java certificate path checkin for proxy certs in SSL with plugins for tomcat and axis.	1.7.3	../../../../../../../glite-web/egee/packages/R1.4/R20050916/bin/rhel30/noarch/RPMS/glite-security-trustmanager-1.7.3-1.noarch.rpm
glite-security-util-java	The java utilities library for security	1.1.2	../../../../../../../glite-web/egee/packages/R1.4/R20050916/bin/rhel30/noarch/RPMS/glite-security-util-java-1.1.2-2.noarch.rpm
glite-security-utils-config	gLite Security Utilities configuration files	1.0.4	../../../../../../../glite-web/egee/packages/R1.4/R20050916/bin/rhel30/noarch/RPMS/glite-security-utils-config-1.0.4-1.noarch.rpm
glite-security-voms-admin-client	gLite VOMS Administration clients	1.0.7	../../../../../../../glite-web/egee/packages/R1.4/R20050916/bin/rhel30/noarch/RPMS/glite-security-voms-admin-client-1.0.7-1.noarch.rpm
glite-security-voms-admin-interface	gLite VOMS Administration service (interface)	1.0.2	../../../../../../../glite-web/egee/packages/R1.4/R20050916/bin/rhel30/noarch/RPMS/glite-security-voms-admin-interface-1.0.2-1.noarch.rpm
glite-security-voms-admin-server	gLite VOMS Administration service	1.2.2	../../../../../../../glite-web/egee/packages/R1.4/R20050916/bin/rhel30/noarch/RPMS/glite-security-voms-admin-server-1.2.2-1.noarch.rpm
glite-security-voms-api	Change me !!!	1.6.5	../../../../../../../glite-web/egee/packages/R1.4/R20050916/bin/rhel30/i386/RPMS/glite-security-voms-api-1.6.5-0.i386.rpm
glite-security-voms-api-c	Change me !!!	1.6.5	../../../../../../../glite-web/egee/packages/R1.4/R20050916/bin/rhel30/i386/RPMS/glite-security-voms-api-c-1.6.5-0.i386.rpm
glite-security-voms-api-cpp	Change me !!!	1.6.5	../../../../../../../glite-web/egee/packages/R1.4/R20050916/bin/rhel30/i386/RPMS/glite-security-voms-api-cpp-1.6.5-0.i386.rpm
glite-security-voms-clients	Change me !!!	1.6.5	../../../../../../../glite-web/egee/packages/R1.4/R20050916/bin/rhel30/i386/RPMS/glite-security-voms-clients-1.6.5-0.i386.rpm
glite-security-voms-config	Change me !!!	1.6.5	../../../../../../../glite-web/egee/packages/R1.4/R20050916/bin/rhel30/i386/RPMS/glite-security-voms-config-1.6.5-0.i386.rpm
glite-security-voms-mysql	Change me !!!	1.1.1	../../../../../../../glite-web/egee/packages/R1.4/R20050916/bin/rhel30/i386/RPMS/glite-security-voms-mysql-1.1.1-0.i386.rpm
glite-security-voms-server	Change me !!!	1.6.5	../../../../../../../glite-web/egee/packages/R1.4/R20050916/bin/rhel30/i386/RPMS/glite-security-voms-server-1.6.5-0.i386.rpm
glite-voms-server-mysql-config	gLite VOMS Server and Admin Tools node configuration files	2.1.0	../../../../../../../glite-web/egee/packages/R1.4/R20050916/bin/rhel30/noarch/RPMS/glite-voms-server-mysql-config-2.1.0-0.noarch.rpm

4. Dependencies

The gLite Computing Element module has the following dependencies:

Component name	Version	RPM file name
GPT	VDT 1.2.2	../../../../../../../glite-web/egee/packages/externals/bin/rhel30/RPMS/gpt-VDT1.2.2rh9-1.i386.rpm
VDT Globus Essentials	VDT 1.2.2	../../../../../../../glite-web/egee/packages/externals/bin/rhel30/RPMS/vdt_globus_essentials-VDT1.2.2rh9-1.i386.rpm
MySQL-server	4.1.11	../../../../../../../glite-web/egee/packages/externals/bin/rhel30/RPMS/MySQL-server-4.1.11-0.i386.rpm
MySQL-client	4.1.11	../../../../../../../glite-web/egee/packages/externals/bin/rhel30/RPMS/MySQL-client-4.1.11-0.i386.rpm
perl-Crypt-SSLeay	0.51	../../../../../../../glite-web/egee/packages/externals/bin/rhel30/RPMS/perl-Crypt-SSLeay-0.51-4.i386.rpm
perl-Authen-SASL	2.08	../../../../../../../glite-web/egee/packages/externals/bin/rhel30/RPMS/perl-Authen-SASL-2.08-1.1.el3.rf.noarch.rpm
perl-Digest-HMAC	1.01	../../../../../../../glite-web/egee/packages/externals/bin/rhel30/RPMS/perl-Digest-HMAC-1.01-11.1.noarch.rpm
perl-Digest-SHA1	2.01	../../../../../../../glite-web/egee/packages/externals/bin/rhel30/RPMS/perl-Digest-SHA1-2.01-15.1.i386.rpm
perl-MIME-Lite	2.117	../../../../../../../glite-web/egee/packages/externals/bin/rhel30/RPMS/perl-MIME-Lite-2.117-2.1.el3.rf.noarch.rpm
perl-Net-Jabber	2.0	../../../../../../../glite-web/egee/packages/externals/bin/rhel30/RPMS/perl-Net-Jabber-2.0-1.1.el3.rf.noarch.rpm
perl-Net-XMPP	1.0	../../../../../../../glite-web/egee/packages/externals/bin/rhel30/RPMS/perl-Net-XMPP-1.0-1.1.el3.rf.noarch.rpm
perl-SOAP-Lite	0.60a	../../../../../../../glite-web/egee/packages/externals/bin/rhel30/RPMS/perl-SOAP-Lite-0.60a-1.1.el3.rf.noarch.rpm
perl-XML-Stream	1.22	../../../../../../../glite-web/egee/packages/externals/bin/rhel30/RPMS/perl-XML-Stream-1.22-1.1.el3.rf.noarch.rpm
Tomcat5	5.0.28	../../../../../../../glite-web/egee/packages/externals/bin/rhel30/RPMS/tomcat5-5.0.28-10_EGEE.noarch.rpm
Java SDK/JRE	1.4.2	http://java.sun.com/j2se/1.4.2/download.html

5. Known bugs and issues

This release has the following bugs and issues. Bug numbers refer to the gLite Bug Tracking system database hosted on the CERN Savannah system at https://savannah.cern.ch/bugs/?group=jra1mdw .

5.1. Known open bugs

Bug number	Description
#7164	glite-voms-init still uses deprecated -hours option
#5848	edg-voms-make-vo-rpms 0.7.4 fails to build RPM
#7898	voms-proxy-init: --certdir parameter description is not clear
#8021	VOMS test script doesn't tell you the progress when in the mass voms-proxy-* fase.
#9171	[VOMS Admin] Tomcat group check too restrictive
#10702	VOMS connecting to database twice
#10805	[VOMS] Failed checks for Expat in configure
#10581	VOMS: problems compiling on debian
#9178	voms/vomrs tomcat5 dies out of memory
#10680	Bad behaviour of java VOMS parser
#7634	VOMS ldap synch and signing policies
#7662	references to EDG license in voms
#7663	edg licence in voms-admin
#8582	voms webui: Couldn't find the configuration file.
#9089	Problems assigning VOMS roles
#9173	[VOMS Admin] VOMS must be in gLite location
#9218	[VOMS Admin] voms-admin fails with SSL and non-standard certificate dir
#9339	VOMS Admin: Host cert information is outdated
#9340	VOMS Admin: Host cert must be easily downloadable from the web interface
#9560	[VOMS Admin] Implement user privilage summary page
#9562	[VOMS Admin] Don't list operations that the user will not be able to execute
#9577	VOMSValidator throws exception if directory /etc/grid-security/vomsdir/ does not exist
#10072	no tool to migrate VOMS db content from MySQL to Oracle
#10363	voms-admin script sets file permissions incorrectly
#10434	voms server update for a vo not possible
#10383	voms-admin-install handles command line options incorrectly
#10386	voms-admin-configure prints out wrong mysql port in help
#10433	voms-admin-configure help is incorrect
#10296	[VOMS]certificate registration command does not pick up CA URI
#10025	VOMS: voms-server-conf.py error
#10037	VOMS Admin needs to have a maillinglist functionality
#10313	VOMS new user - invalid email
#10399	glite-mkgridmap truncates gridmap file, when VOMS server is down
#10423	[VOMS] glite-voms-server.cfg.xml should offer to specify authentication params for smtp
#10431	VOMS admin and VOMS need to be harmonized
#10728	Java VOMS class should return clean FQAN
#10729	VOMS API should return clean FQAN
#10761	[VOMS] Empty error message when doing vom-proxy-init with invalid line in vomses-file
#10785	[VOMS] missing implicit permissions on VOMS admin interface
#10813	[VOMS] Oracle Error on confirm registration request
#10846	[VOMS] Must specify alternate port and socket for MySQL
#10163	No way to have voms core restarting after machine reboot
#9151	voms-admin doesn't send notification to admins
#3887	VOMS and user name assignment
#8508	voms deployment scripts drop all VO members on a rerun.
#9795	VOMS deployment script downloads old CA certs version
#9804	VOMS deply script: no check on empty parameters
#10050	VOMS installation does not allow to install from an existing VOMS setup
#10336	Data Single Catalog: no mention to voms in the documentation
#10847	WMSproxy doesn't manage to submit : VERR_SIGN voms sign verify error

5.2. Fixed in this or previous releases, but not yet tested

Bug number	Description
#6049	lcas-plugins-voms does not support FQANs, only old style VOMS-triplets
#7048	VOMS: there is no easy way for an application to retrieve the info from the proxy cert
#10678	[VOMS]glite-voms-server-config.py fails with several switches
#6503	GridSite does not export VOMS extensions to the cgi environment
#6943	If the user issuing voms-proxy-init is not a member of the specified VO, confusing error is returned.
#7047	VOMS_Retrieve() segfaults if VERIFY_DATE is set and the proxy has expired
#7369	Error from voms-proxy-init
#8867	memory leak in lcmaps voms group plugins
#9408	VOMS Admin spits internal database inconsistency faults on getGridmapUsers
#10253	VOMS (core) service rejects connection because of not able to write to logfile
#10422	VOMS client lib./MyProxy: Globus deallocation problem
#4637	VOMS API should offer a simpler way of processing the VOMS attribute certs
#5166	[VOMS Admin] Couldn\\\'t handle the Russian CA issued personal certificates
#5357	ambiguous error message in edg-voms
#5360	edg-voms creates logfile with exotic mode
#5362	edg-voms run as a non-privileged user
#5849	LCMAPS VOMS plugin 0.0.30 crashes on SLC3
#6678	VOMS_Contact() crashes
#7311	voms build does not use expat.location from the repository
#7511	VOMS_FindByVO() doesn't work without user's local configuration
#7660	hard-wired defaults in voms_install_db
#7665	rvoms-admin-configure as pm post install script
#7890	VOMS attribute validation fails in java VOMS parser
#7905	Support for GLOBUS_FLAVORS needed by broker missing in VOMS.
#8012	glite-security-voms-admin-server installed before tomcat user exists.
#8295	Welcome to VOMS! doesn't tell you the VO name
#8357	org.glite.security.voms/src/configure.in bug when checking for GLOBUS_FLAVORS
#8603	VOMS (core) service can't restart after crash when log file is at 2GB.
#9049	Mail from VOMS refers to edg
#9077	voms-proxy-init man page should include role syntax
#9168	[VOMS Admin] --fileinstall switch to voms-admin-configure fails
#9170	[VOMS Admin] --fileinstall still requires valid MySQL location
#9799	[VOMS] The edg-voms process loops on accept() when the port number is unavailable
#9800	[VOMS] The edg-voms process truncates the log file on startup
#10069	VOMS administration webservice removes user from VO instead of group
#10432	voms_install_db has no help function
#10459	glite-security-voms-oracle should not depend on oracle rpms
#10574	voms-proxy-init prints wrong error message when cert expired
#10682	Man pages missing from separate voms rpms
#6763	VOMS server certificate not installed by CE installer
#8682	After the Single Catalog (MYSQL) installation /etc/grid-security/vomsdir is not created
#9342	CE LCMAPS: Can't alter the VOMSDIR for in the lcmaps.db file through XML conf file
#10189	UI configuration does not alter vomses file

5.3. Bugs closed since last release

This release fixes the following bugs and issues. Bug numbers refer to the gLite Bug Tracking system database hosted on the CERN Savannah system at https://savannah.cern.ch/bugs/?group=jra1mdw

Bug number	Description
#3739	VOMS registration error
#4120	[VOMS] Requesting VO membership confirmation e-mails were not send to user.
#4122	[VOMS] In the request detail the E-Mail address =<null>
#4484	Can't setup a VOMS server with a VO name longer then six characters
#5009	VOMS: making it possible to assign roles more freely
#5048	No RPMS for the VOMS Admin (interface)
#5356	unecessary file org.glite.security.voms/src/include/config.h.in
#5358	edg-voms has no help/usage option
#5359	edg-voms exits abnormally when given unrecognised optionoption
#5403	org.glite.security.voms-admin-server fails to build
#5454	LCAS voms_plugin initialization failure : libgridsite.so.1.0 contains an undefined symbol
#5495	Can\'t execute voms-admin-configure because of missing module
#5561	[VOMS Admin] Couldn't send e-mail for the registration request
#5582	unable to get voms proxy info from a voms proxy
#5803	voms-proxy-init requires vomses confile to owned by root user
#5817	Cannot connect to the VOMS
#6060	voms_install_db cannot be run properly with MySQL relocated
#6424	VOMS Admin can't send notification emails to users
#6428	VOMS lock files are going into the wrong place
#6612	voms-admin requires following patch on voms core
#6857	Is it still possible to select the VOMS groups with voms-proxy-init?
#6930	VOMS & VOMS Admin services should publish to the Service table
#7011	glite-voms-server-config DBA password should be optional
#7193	[VOMS Admin] The mechanism for getting notification addresses for admin users does not work
#7243	Access denied error on GLOBAL ACL section of VOMS Admin
#7303	glite CE configuration module should download voms cert
#7453	glite-voms-server-config.py dies with unknown error
#7583	voms-proxy-init fails if vomses file contains empty lines at the end
#7695	ohne worte ( 6 minutes or 2 months ? ) voms-proxy-init -hours
#7696	voms-admin request details not complete
#7813	voms-proxy-init wrong pass phrase error message should include \n
#7925	voms-proxy-init crashes on my new certificate
#7986	Unreplaced tokens in VOMS Admin web interface
#7989	VOMS Admin confirmation messages display (null) instead of VO name
#7990	The vomses example file is missing from the VOMS Admin installation
#8006	voms-admin-server and role attribute
#8036	VOMS server upgrade fails due to conflicts
#8092	Multiple "/opt/glite/var/etc/voms-admin/<VO name>/vomses" file problems
#8343	voms_install_db.sgml problem
#8531	Problem to start the VOMS server - conflict with detected DB version
#8605	Errors in the glite-voms-server.cfg.xml file
#8639	problem with voms-admin-configure
#8641	problem with user creation through glite voms-admin
#8750	VOMS Server uses a blocking socket
#8756	VOMS install script fails on XML parsing of the .cfg.xml file
#8868	[VOMS Admin] Subgroup creation is not possible on the web interface
#8869	[VOMS Admin] Multiple vomsd configuration problems in voms-admin-configure
#9085	VOMS display shows everyone in each group even if empty.
#9129	VOMS test script isn't in the release
#9172	[VOMS Admin] Allow for alternate invocation methods for MySQL
#9254	SQLPLUS libs is packed with VOMS and breaks standard install
#9302	VOMS-admin Welcome page
#9561	[VOMS Admin] Implement implicit permissions
#9576	VOMS fails to verify VOMS server certificate the first time after a VOMS_Init
#9596	voms-proxy-info doesn't validate the signature
#9949	glite-mkgridmap 2.4.2 not working with voms-admin 1.0.5
#10009	libvomsc library depends on c++ symbols
#10044	voms-proxy-init lack of a newline displaying the help
#10049	VOMS Admin Global ACL needs to be changed on deployment
#10051	VOMS installation doesn't allow to enter a SMTP host in the XML file anymore
#10137	VOMS Admin getGridmapUsers fails if a container is not explicitly passed
#10203	glite R1.2 voms core doesn't start - misleading error message
#10267	[VOMS] installer script error
#10424	[VOMS]Missing information in glite-voms-server.cfg.xml-file
#10425	voms-proxy-init bingo puzzle
#10430	VOMS server Oracle crashes on user registration
#10439	VOMS Admin cannot manage more than one VO installation
#10441	VOMS admin does not allow to be run on MySQL db without password
#10442	VOMS admin points always to last vo when using one VO
#10496	[VOMS] java.lang.NullPointerException
#10545	VOMS server installation: voms-proxy-init failing with globus_gss_assist token :3: read failure: Connection closed
#10673	strange voms-proxy-init behaviour
#10734	[VOMS] glite-voms-server-config.py --configure does not parse second instance in glite-voms-service.cfg.xml correctly
#10786	VOMS: installer fails with oracle instanclient dependencies
#10827	voms-proxy-init crashes because of proxy-format error
#10839	VOMS: 4Suite, CA list,, perl-libxml, rgma-servicetool-config and other missing dependencies