EMI 1 Kebnekaise Products

Full list of 56 EMI 1 Kebnekaise Products, with detailed release notes and instructions for their installation/configuration.

Products list

What's new:

Voms packaging has been changed to install into system directories. For example, this means that executables are in /usr/bin, /usr/sbin, configuration files in /etc/voms, etc...
A REST interface is available to obtain VOMS attribute certificates.
There are no longer dependencies on globus anywhere. However, on-the-wire compatibility with previous versions of VOMS is still maintained.
Compatibility with EPEL installation.
Installation/Configuration: https://twiki.cern.ch/twiki/bin/view/EMI/VOMSystemAdministratorGuide

Known Issues:

Due to a memory leak discovered in VOMS Java APIs 2.0.9 this version was deprecated, and a rollback to the 2.0.8 codebase is provided in EMI repositories with the 2.0.9-2 version:
- voms-api-java-2.0.9-2
- voms-api-java-javadoc-2.0.9-2
Possible affected services: - ARGUS, StoRM-GridHTTPS-server
To apply the rollback, after checking if version 2.0.9-1 is present on your node, execute the following:
# yum clean all # yum upgrade voms-api-java
Affected services need also a restart:
- ARGUS, in this order:
  # service argus-pap restart # service argus-pdp restart # service argus-pepd restart
- StoRM-GridHTTPS-server
  # service tomcat5 restart

Extended release notes

The following notes apply to this release of VOMS.

All the globus_flavor versions of the APIs have disappeared. They are not present in the EPEL release, and there was no reason why they should appear here. Link to the plain library instead.
The libvomsc.so library has disappeared. It was deprecated since 2006, and since 2006 libvomsapi offered both the C and C++ interfaces. Link to that instead. Indeed, libvomsc for four years has been nothing else than a renamed libvomsapi.
Globus is no longer a dependency, neither at buildtime nor at runtime. Since the library only used OpenSSL, and the Globus we got from VDT uses the system OpenSSL anyway, there was no reason to continue depending on Globus. This has some consequences on the usage of libvomsapi in a threaded environment, see the section about thread in release notes of this patch (http://savannah.cern.ch/patch/?2717) for details
Those same notes also mention that as a consequence, the RetrieveFromCtx() function/method is no longer available. It was not a widely used function anyway, and example code on how to obtain the same functionality may be easily obtained by writing one's own version.
As a consequence of all the previous points, the new libraries are incompatible at the ABI level with the ones in EGEE, and consequently have had their version increased to one.
Until the globus bug referred in savannah bug #81663 (https://savannah.cern.ch/bugs/?81633) is fixed, the --policy option of voms-proxy-init (and grid-proxy-init if you have it installed) MUST NOT be used.