> -----Original Message-----
> From: Testbed Support for GridPP member institutes [mailto:TB-
>
> I've been waiting for a little extra information before writing to the
> users list since many of us have had the expiry notification. What the
> notification does not tell you is that after the last CA event all
> (minus a few!) UK users were registered via VOMRS with both their now
> expired certificate and the new one (which you have recently started
> using). I suspect in your case you are one of the "minus a few" who
got
> overlooked in one of the registrations (for ATLAS).
>
I wonder if this is a matter of timing - I've only been registered in
the atlas VO since the end of April this year, so if the change was made
before that, then I subsequently registered with my old certificate and
the change process wasn't re-run we'd have got to this situation.
> If the old certificate had not yet expired you could do the update via
> VOMRS yourself. The easiest way to fix it now (assuming this is the
> reason) is to contact the VO admin directly and explain that you are
> now using a certificate with the new CA DN.
>
Right-o. I'll GGUS them.
> -----Original Message-----
> On Behalf Of Alessandra Forti
>
> Maybe Ewan updated his certificate (and therefore the issuer DN) with
> dteam but not with atlas.
>
Of the three VOs I'm in I've done a full from-scratch re-registration
for
vo.southgrid.ac.uk on the gridpp VOMS, and done nothing at all for the
two
hosted at CERN.
Ewan
|