I'd need more info on how the client is configured to make an authoritative statement about CertWizard's MyProxy Uploader interface. It can talk to abritrary MyProxy servers
over arbitrary ports and usernames. So if that is all a common interface it should be OK.
Having said that, having looked at the client example given:
---
$ ./myproxy-logon -s localhost -n -l steve@local -o /tmp/creds.pem
The client will prompt for the steve's password and finishes saying
---
I have a few comments:
1. A myproxy server name of "localhost" means this client code is only going to work
where a/the myproxy server is setup (from what I can guess anyway).
2. I thought the "-n" option was to not prompt for a passphrase, yet comment says it does
So I am doubly confused.
BTW I know some (many?) of you use CertWizard for obtaining/renewing user/host certificates,
but how many of you use it for the MyProxyUploader part of the interface? How about
the VOMS-enabled bits?
How about your users?
Cheers
JK
> -----Original Message-----
> From: Testbed Support for GridPP member institutes [mailto:TB-
> [log in to unmask]] On Behalf Of Christopher J. Walker
> Sent: Wednesday, November 14, 2012 1:31 PM
> To: [log in to unmask]
> Subject: Re: Moonshot briefing just about to start
>
> On 14/11/12 12:22, Christopher J. Walker wrote:
> > https://www.ja.net/events/moonshot-online-briefing
> >
> > 12:30-13:30 today.
> >
> > Chris
>
>
> http://www.project-moonshot.org/devwiki/testing/myproxy/
>
> may be relevant to us.
>
> I'm not sure how that fits in with certiwizard.
>
> Chris
--
Scanned by iCritical.
|