gLite 3.1
glite-LFC_mysql - Update to version 3.1.17-0
|
Date |
02.04.1009 |
Priority |
Normal |
Description
Documentation:
VOMS Core Services User Guide: https://edms.cern.ch/file/973684/1/voms-guide.pdf
VOMS Admin User Guide: https://edms.cern.ch/file/974094/1/voms-admin-user-guide.pdf
VOMS Installation and Configuration Guide: https://edms.cern.ch/file/974982/1/voms-installation-configuration-guide.pdf
Contains a fix for bug #38506 (Previous Predictable Order with --voms flags was lost.). Now the order of FQANs in the VOMS proxy follows the order in which FQANs are specified on the command line as values of the "-voms" options. This does _not_ apply to the shorthand "<voname>:/Role=<role>" syntax.
Known issues:
The scripts for configuring MySQL replication (/opt/glite/libexec/voms/voms_replica_master_setup.sh and /opt/glite/libexec/voms/voms_replica_slave_setup.sh) do not work properly. They should not be used. The VOMS Core Services User Guide contains a description on how the replication works. Together with the replication scripts this description can used to do the replication manually.
Developer changes:
New API added for the C and C++ APIs. VOMS_SetVerificationTim(time_t time).
As usually, except where noted, everything is backwards-compatible with previous version, both on the protocol level (i.e. client and server versions may be freely mixed) and ABI level (API libraries can be upgraded with newer versions without needing recompilation of the linking parties).
Please also have a look at the list of known issues.
This update fixes various bugs. For the full list of bugs, please see list below.
Fixed bugs
Number | Description |
#39625 |
VOMS-CORE: Cannot specify two or more --voms options for the same VO in the command line |
#41094 |
VOMS-CORE: requesting an unassigned role does not return an error |
#41095 |
VOMS-CORE: request fails when requesting a role that is not assigned |
#41116 |
VOMS-CORE: -noregen functionality is broken |
#41773 |
[VOMS-CORE] No error reported when non-existent group requested |
Updated rpms
The RPMs can be updated using yum via
Service reconfiguration after update
Not needed.
Service restart after update
Not needed.
How to apply the fix
- Update the RPMs (see above)
- Update configuration (see above)
- Restart the service if necessary (see above)
|
|