Fix committed in org.glite.wms. It consists in the replacement of GLOBUS_LOCATION with WMS_LOCATION_USR in the shell script.

To test it, it's just sufficient to upgrade the glite-wms-purger rpm and execute:

grep "grid-proxy-init" /usr/sbin/glite-wms-create-proxy.sh

which should print out:

proxy=`"${WMS_LOCATION_USR}/bin/grid-proxy-init" -q \

They have already verified that this substitution on the script solves the problem of 512bit generated proxy. Read carefully the related ticket and the related ones because this issue is tightly related to WMS-114.

In fact the missing variable GLOBUS_LOCATION avoids the invocation of grid-proxy-init, which by default produces 1024bit proxies.
But we observed that the proxy is still updated; by what ? by an internal mechanism of the wms purger which uses internal an hard-coded value (512bit) for the proxy generation (issue WMS-114).

When issue WMS-113 is solved, the proxy are correctly generated with 1024bit because grid-proxy-init is invoked by the cron; but the purger still has the hard-coded value of 512bit in it's proxy_init() function. Then, if the cron fails for some reason, because of WMS-114 issue the proxy goes back to 512bits.

Fix to WMS-114 makes sure the the WMS's proxy will always be generated with 1024bits.