TWiki> LCG Web>LCGGridDeployment>LcgDocs>VOMS (revision 1)EditAttachPDF

VOMS Server Guide

Service Overview

VOMS serves as a central repository for user authorization information, providing support for sorting users into a general group hierarchy, keeping track of their roles, etc. Its functionality may be compared to that of a Kerberos KDC server. The VOMS Admin service is a web application providing tools for administering member databases for VOMS, the Virtual Organization Membership Service.

VOMS Admin provides an intuitive web user interface for daily administration tasks and a SOAP interface for remote clients. (The entire functionality of the VOMS Admin service is accessible via the SOAP interface.) The Admin package includes a simple command-line SOAP client that is useful for automating frequently occurring batch operations, or simply to serve as an alternative to the full blown web interface. It is also useful for bootstrapping the service. The VOMS server can use MySQL or ORACLE as a backend.

VOMS Node Installation

The general steps to install the OS and the gLite-VOMS 3.1 server are explained at:

Upgrading from a gLite 3.0 VOMS Server

This section describes the necessary steps if you are migrating from a 3.0 VOMS server. Please read these instructions carefully before starting the upgrade process!

Besides switching to a new base operating system (from SL3 for the gLite 3.0 release series to SL4 for the gLite 3.1 release series), the gLite 3.1 VOMS server comes with the redesigned version 2 of VOMS-ADMIN which uses a new database schema. The old VOMS databases must therefore be upgraded for the gLite 3.1 VOMS server.

You are strongly advised to backup your database before doing the upgrade!

The database upgrade program is part of the VOMS-ADMIN 2 release and it will be automatically installed on your new server.

Also, the database upgrade will only work if you are using the latest database schema in production from the gLite 3.0 VOMS server.

You should complete successfully all database upgrades before running the VOMS configuration script (

Before proceeding with the database upgrade you should decide whether you want to keep the old database instance or if you want to create a new one. If you run VOMS 3.0 with a MySQL database backend on the same machine you will probably want to use a new database instance on the 3.1 VOMS node as the node also needs to be updated to the new OS. In this case you can copy the dumped database to the new host and then run the database upgrade script against the new instance on the new node.

Migrating the database to the new node

To migrate the database to the new node you need to do the following steps:

  • Dump the old database on the old VOMS server and transfer the file to the new node

       mysqldump -h <OLD_HOSTNAME> -u <USER> -p --databases <DB_NAME> > <DUMP_FILE>

  • Use the database dump on the new machine to create the new database

       mysql -h <NEW_HOSTNAME> -u <PRIV_USER> -p < <DUMP_FILE>

  • Grant ALL PRIVILEGES to the user that VOMS-ADMIN will use to connect to and use the database

       mysql -h <NEW_HOSTNAME> -u <PRIV_USER> -p

              TO <VOMS_USER>@localhost

Migrating the VOMS configuration to the new node

  • Copy all configuration files *.cfg.xml from /opt/glite/etc/config on the old gLite 3.0 VOMS server node to the new node (in the same place)

  • Copy recursively all subdirectories from /var/glite/etc/voms-admin named after the VOs you want to upgrade to the new node (in the same place)

  • In each of these subdirectories check the file. It contains the database connection parameters. Edit these on the new 3.1 server if needed (they should point to the database you want to upgrade).

  • Copy the certificates of the VO administrators to the new server (pointed by the value of the voms.admin.certificate VO-level parameter)

Upgrading the database schema

Before you proceed make sure that the database is not in use by someone else as the following steps will modify the database schema! To actually upgrade the database you need to:

  • Set the following variables with the appropriate values

       export GLITE_LOCATION=/opt/glite
       export GLITE_LOCATION_VAR=/var/glite
       export GLITE_LOCATION_LOG=/var/log/glite

  • In each VO subdirectory located under /var/glite/etc/voms-admin check the file. It contains the database connection parameters. Edit these on the new 3.1 server if needed (they should point to the database you want to upgrade).

The format of this file will change after the upgrade because VOMS-ADMIN 2 uses Hibernate as a persistence layer.

  • For each VO database you want to upgrade run:

       /opt/glite/sbin/voms-admin-configure --vo=<VO_NAME> upgrade

Note: In case of an unexpected error during the upgrade of a VO, its corresponding file might be left in the new format. To rerun the upgrade you will have to restore the old one manually.

All known upgrade issues are resolved in VOMS-ADMIN 2.0.17.

Updating the configuration

You can continue to use the old configuration files but you will probably need to change the following variables:

  • JAVA_HOME (in glite-global.cfg.xml)
  • CATALINA_HOME (in glite-global.cfg.xml)
  • (in glite-global.cfg.xml)
  • (in glite-global.cfg.xml)
  • fetch-crl.script (in glite-security-utils.cfg.xml) It should point to the actual location of the fetch-crl executable (normally /usr/sbin/fetch-crl on gLite VOMS 3.1 host).
  • voms.db.oracleinstantclient.location (in glite-voms-server.cfg.xml if you are using Oracle as backend)
  • voms.admin.certificate (per-VO parameter) Its value should be a valid path to a PEM file containing the certificate of the VO administrator.

Also make sure you are using the desired database connection parameters for the VO (in the volist.cfg.xml file)

Reconfiguring the VOMS server

Reconfigure the VOMS server by executing:

/opt/glite/etc/config/scripts/ --configure

Starting the VOMS server

Start the VOMS server by executing:

/opt/glite/etc/config/scripts/ --start

Configuring access for gridmap file generation

This step needs an appropriate environment being set up for running the voms-admin CLI on the voms host. This can be done either by running:

[root@vomshost: ~] # . /etc/glite/profile.d/

or by restarting the shell session with the server (It is loaded automatically for new sessions with the VOMS host).

For successful gridmap file generation on the relevant grid hosts, the appropriate access rights should be granted for each VO. This can be done via the voms-admin command line interface. The following command grants the necessary rights to the predefined user “Anyone” (any user that presents a valid certificate issued by a trusted CA) for the top group “/” and its descendants (the TRUE flag triggers recursive operation).

voms-admin --vo=<VO_NAME> --nousercert add-ACL-entry /<VO_NAME> ANYONE VOMS_CA 'CONTAINER_READ,MEMBERSHIP_READ' TRUE

Registration of the VOMS host identity as a default admin

This step should be performed only if the VOMS host will have a new hostname or for any reasons the subject of its host certificate differs from the one that was installed on the gLite VOMS 3.0 host. For each VO, execute the following command on the VOMS host:

/opt/glite/sbin/ add-admin --vo <VO_NAME> --cert /etc/grid-security/hostcert.pem

Verification of the ACL configuration

VOMS-ADMIN 2 has a redesigned security model. The global ACL is now deprecated. If you had set up custom ACEs in VOMS-ADMIN 1, inspect the ACLs of the groups hierarchy after the upgrade is complete. Consult the VOMS-ADMIN-2 Users guide on how the access control mechanism works in the new version.

VOMS Node Configuration

-- DimitarShiyachki - 01 Jul 2009

Edit | Attach | Watch | Print version | History: r5 | r4 < r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r1 - 2009-07-01 - DimitarShiyachki
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    LCG All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback