Before I raise this as a GOCDB issue can someone with a new certificate
please try accessing GOCDB with IE?
John
> -----Original Message-----
> From: Testbed Support for GridPP member institutes
> [mailto:[log in to unmask]] On Behalf Of Ma, M (Mingchao)
> Sent: 13 January 2008 15:29
> To: [log in to unmask]
> Subject: Re: GridPP VOMS certificate
>
> Hi Yves,
>
> If you can not instantiate dteam voms proxy with your new
> certificate, then you need follow Alessandra's wiki. As John
> mentioned, you do not need to re-register if your old one is
> still valid. The problem I mentioned in my previous email is
> different. There is no problem for Marian to use his
> certificate as a dteam member (he actually re-register his
> new certificate since his old one expired before he got his
> new one). What he can not do at the moment is to use his web
> browser with his new certificate to access gocdb website
> (https://goc.gridops.org), which is very strange since he can
> use the same certificate to access cic portal, SAM etc via
> https. Could you please load your new certificate into your
> web browser and try to access gocdb (please make sure that
> your old certificate is not loaded into your browser), please
> let me know if you can access it or you get the same error
> information (firefox error code: -12227).
>
> Cheers,
>
> Mingchao
>
>
> > -----Original Message-----
> > From: Testbed Support for GridPP member institutes
> > [mailto:[log in to unmask]] On Behalf Of Gordon, JC (John)
> > Sent: 11 January 2008 21:22
> > To: [log in to unmask]
> > Subject: Re: GridPP VOMS certificate
> >
> > Yves, you don't need to unregister, you can load the new
> certificate
> > while the old one is valid. See the wiki Alessandra pointed
> to earlier
> > today.
> >
> > John
> >
> > > -----Original Message-----
> > > From: Testbed Support for GridPP member institutes
> > > [mailto:[log in to unmask]] On Behalf Of Yves Coppens
> > > Sent: 11 January 2008 19:20
> > > To: [log in to unmask]
> > > Subject: Re: GridPP VOMS certificate
> > >
> > > Hi Mingchao,
> > >
> > > I have exactly the some problem with my renewed certificate.
> > > I also cannot instantiante dteam voms proxy any longer. The
> > DN of the
> > > UK CA has changed, so for the voms at least, I guess I
> will have to
> > > un-register and re-register.
> > >
> > > This will affect true VO users too.
> > >
> > > Thanks,
> > >
> > > Yves
> > >
> > >
> > > On Fri, 11 Jan 2008, Ma, M (Mingchao) wrote:
> > >
> > > > Thanks, Alessandra. I do observe another very strange
> > > problem. Marian
> > > > at RAL just got his new certificate last week since his old one
> > > > expired. He experienced very strange problem with GOCDB
> > > (https://goc.gridops.org).
> > > > The problem seems to be that gocdb web server does not
> > > recognise his
> > > > new certificate (has removed the old one and loaded new
> > one into his
> > > > browser) for some reason. The error code is -12227.
> > However he can
> > > > access (https) cic portal, SAM website with his new certificate
> > > > without any problems. Does anyone else experience the
> > same problem:
> > > > Can't access gocdb with your new certificate, but have no
> > > problem to
> > > > access other https sites?
> > > >
> > > > Cheers,
> > > >
> > > > Mingchao
> > > >
> > > >> -----Original Message-----
> > > >> From: Testbed Support for GridPP member institutes
> > > >> [mailto:[log in to unmask]] On Behalf Of
> Alessandra Forti
> > > >> Sent: 11 January 2008 16:58
> > > >> To: [log in to unmask]
> > > >> Subject: GridPP VOMS certificate
> > > >>
> > > >> Hi,
> > > >>
> > > >> there are few users having difficulties because of the
> > VOMS and CA
> > > >> certificates update. I've updated the wiki section about this:
> > > >>
> > > >> https://www.gridpp.ac.uk/wiki/Instruction_for_VO_administrator
> > > >> s#NEWS_on_VOMS_configurations_etc
> > > >>
> > > >> Please follow the instruction there and let use know if
> > > you find any
> > > >> difficulty.
> > > >>
> > > >> cheers
> > > >> alessandra
> > > >>
> > > >> PS I know, I know rpm and yum/apt repository in the pipeline.
> > > >>
> > > >
> > >
> >
>
|