While investigating problem with secondary collectors for VOFrontend, I discovered that there existed a bug affecting the WMS collector condor data. It was not populating the collector data at all and so long as you were using the default data, all was well.  This did correct a problem I was seeing when a VOMS proxy was being used to communicate with the WMS collector where it would not ignore the VOMS attributes.  The COLLECTOR.USE_VOMS_ATTRIBUTES that was missing was the culprit.  This did not affect the user collector.
While investigating problem with secondary collectors for VOFrontend, I
discovered that there existed a bug affecting the WMS collector condor data.
It was not populating the collector data at all and so long as you were using
the default data, all was well.  This did correct a problem I was seeing when
a VOMS proxy was being used to communicate with the WMS collector where it
would not ignore the VOMS attributes.  The COLLECTOR.USE_VOMS_ATTRIBUTES
that was missing was the culprit.  This did not affect the user collector.

holzman/glideinwms-old,holzman/glideinwms-old,holzman/glideinwms-old