Hi all,
On 24/06/15 18:02, Basney, Jim wrote:
I agree. MyProxy offers 3 options for adding VOMS attributes to the
credential:
1. adding the VOMS attributes via myproxy-init by calling voms-proxy-init
2. adding the VOMS attributes via myproxy-server using the VOMS APIs
(as requested by
Hi,
the error is on the client side:
Enter MyProxy pass phrase:
failed to run voms-proxy-init: No such file or directory
A credential has been received for user Š
when you run
myproxy-logon -m esr
the myproxy-logon command tries to launch 'voms-proxy-init -voms esr .' and
it fails to
Hi Jan,
I see your point (upload a VOMS enabled proxy, generated locally), but I want
to store on MyProxy a plain proxy (without signature) and retrieve a credential
with a VO extension. It’s MyProxy that should contact the VOMS server to get
the signature. The goal is to avoid to install (and
Hi again Jim,
unfortunately I have the same problem with GT 6.0 (from Sep. 2014).
Versions 5.2.4 and 5.2.5 are fine.
If someone from the GT team is willing to look into that, we can give you
access to
a test machine with the same libraries/setup we used to do our tests.
All the best,
Matteo
Hi Matteo,
Sorry for the slow response. Unfortunately I don't have easy access to a
VOMS environment to try to reproduce the problem you've reported.
I think the VOMS AC doesn't verify message is not a symptom of the
problem. I think you should also see that message from your working GT
5.2.4
85748 Garching b. München (Germany)
Phone: +49 89 35831 8724
From: Basney, Jim jbas...@illinois.edu
Sent: 22 June 2015 19:36
To: Lanati, Matteo
Cc: gt-user@lists.globus.org
Subject: Re: [gt-user] Problems with MyProxy and VOMS support
Hi Matteo,
Sorry
Hi all,
I compiled MyProxy with VOMS support from the latest source tarball available,
linking it against voms version 2.0.10 and openssl 1.0.1h.
I think the result is fine:
- if I do a $GLOBUS_LOCATION/sbin/myproxy-server -V I see myproxy-server
version MYPROXYv2 (v6.1 Jun 2015 PAM VOMS
