VOMS Admin Sign AUP default grace period is too short

Is solution available: solution available in VOMS Admin version 2.7.0 that will be released in EMI 1 Update 17 on May, 17th, 2012 and in EMI 2.

Workaround:

The default grace period can be extended by setting the following option for a given VO:

voms.aup.sign_aup_task_lifetime = 7

The above setting is currently NOT supported by the VOMS YAIM module (support for it will be added in 2.7.0 version). An easy way to set this variable and not having it lost
at each YAIM reconfiguration is by changing the voms.service.properties.template file found in

VOMS Admin does not send warning message before suspending users due to membership expiration

Is solution available: solution available in VOMS Admin version 2.7.0 that will be released in EMI 1 Update 17 on May, 17th, 2012 and in EMI 2.

The bug prevents the sending of e-mail warnings to the VO manager before the user membership expiration.
The lack of this e-mail notification compromises the capability to renew membership in due time, especially in case of large-scale VOs, and when for many users membership expires at the same time.
This is the case for all VOs whose VOMS server was upgraded from gLite 3.1 to gLite 3.2 as during migration the user membership date is reset to the same time.

How to understand which users are about to expire

VOMS Admin version 2.5.3, 2.5.5 and 2.6.1 do not provide an easy way of finding out which users are about to expire. For VOs with limited numbers of users one could query the VOMS Admin web application,
but for large VOs this approach is unbearable.

An easy way of knowing which users are about to expire in the next 30 days is by running a command similar to the one below on the VOMS MySQL database for a given VO (change
the hostname and VO name accordingly to your VOMS installation):