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 OCSP)”, meaning that VOMS support is there - if I look at the executable, I see the dependency from libvomsapi, "libvomsapi.so.1 => /opt/voms/lib/libvomsapi.so.1”. Unfortunately, when I try to retrieve a proxy that I uploaded earlier and ask MyProxy to sign it for me, it fails. The proxy is issued, but without the VO signature. On the client I do
myproxy-logon -m esr and I see Enter MyProxy pass phrase: failed to run voms-proxy-init: No such file or directory A credential has been received for user … Of course I don’t have voms-proxy-init on my client, that’s the whole point of using MyProxy for this task. On the server side I see ... Passphrase matches credentials, and PAM config is "sufficient"; authentication succeeds without checking PAM. Owner: matteo Location: /var/myproxy_test/ ... Max. delegation lifetime: 43200 seconds Sending OK response to client /C=... retrieving proxy Stored Credential is Proxy. VOMS AC doesn't verify. retrieving VOMS User Information. Retrieve esr VO Contact to VOMS Server: voms.grid.sara.nl Delegating credentials for /C=... lifetime=43200 Sending OK response to client /C=... Client /C=... disconnected Is the message "Stored Credential is Proxy. VOMS AC doesn't verify” the symptom of a problem? In the config file I defined allow_voms_attribute_requests true voms_userconf /etc/vomses and it seems that my VO (esr) and the VOMS server have been identified. The whole setup used to work with GT 5.2.4 (compiled from scratch). Is there any suggestion? Best, Matteo Matteo Lanati Distributed Resources Group Leibniz-Rechenzentrum (LRZ) Boltzmannstrasse 1 85748 Garching b. München (Germany) Phone: +49 89 35831 8724
