Project

General

Profile

producing a proxy

Added by Saray Jose over 12 years ago

Hello,

I am trying to generate a proxy with JSAGA, the file i am using is sent as an attachment.

The following output is produced :

Enter UserPass for security context: VOMS1 (VOMS)

[2012-02-10 14:11:53,574] ERROR org.glite.voms.contact.VOMSSocket : Error getting output stream from underlying socket:Authentication failed [Caused by: Failure unspecified at GSS-API level [Caused by: Unexpected message]]
[2012-02-10 14:11:53,574] ERROR org.glite.voms.contact.VOMSProxyInit : Error communicating with server cclcgvomsli01.in2p3.fr:8443:Authentication failed [Caused by: Failure unspecified at GSS-API level [Caused by: Unexpected message]]
[2012-02-10 14:11:53,574] ERROR org.glite.voms.contact.VOMSProxyInit : Error communicating with server cclcgvomsli01.in2p3.fr:8443:Authentication failed [Caused by: Failure unspecified at GSS-API level [Caused by: Unexpected message]]
Exception in thread "main" NoSuccess: org.glite.voms.contact.VOMSException: Error communicating with server cclcgvomsli01.in2p3.fr:8443:Authentication failed [Caused by: Failure unspecified at GSS-API level [Caused by: Unexpected message]]
at fr.in2p3.jsaga.adaptor.security.VOMSSecurityAdaptor.createSecurityCredential(VOMSSecurityAdaptor.java:175)
at fr.in2p3.jsaga.impl.context.ContextImpl.createCredential(ContextImpl.java:281)
at fr.in2p3.jsaga.impl.session.SessionImpl.addContext(SessionImpl.java:63)
at fr.in2p3.jsaga.command.ContextInit.main(ContextInit.java:59)
Caused by: org.glite.voms.contact.VOMSException: Error communicating with server cclcgvomsli01.in2p3.fr:8443:Authentication failed [Caused by: Failure unspecified at GSS-API level [Caused by: Unexpected message]]
at org.glite.voms.contact.VOMSProxyInit.contactServer(VOMSProxyInit.java:390)
at org.glite.voms.contact.VOMSProxyInit.getVomsAC(VOMSProxyInit.java:167)
at org.glite.voms.contact.VOMSProxyInit.getVomsProxy(VOMSProxyInit.java:292)
at fr.in2p3.jsaga.adaptor.security.VOMSProxyFactory.createProxy(VOMSProxyFactory.java:145)
at fr.in2p3.jsaga.adaptor.security.VOMSSecurityAdaptor.createSecurityCredential(VOMSSecurityAdaptor.java:147)
... 3 more
Caused by: org.globus.common.ChainedIOException: Authentication failed [Caused by: Failure unspecified at GSS-API level [Caused by: Unexpected message]]
at org.globus.gsi.gssapi.net.GssSocket.startHandshake(GssSocket.java:150)
at org.globus.gsi.gssapi.net.GssSocket.getOutputStream(GssSocket.java:166)
at org.glite.voms.contact.VOMSSocket.getOutputStream(VOMSSocket.java:185)
at org.glite.voms.contact.VOMSProxyInit.contactServer(VOMSProxyInit.java:379)
... 7 more

My questions are :
1. What is the meaning of the password the system is prompting ?
2. I havent found the correct url for the voms server of vo.rhone-alpes.idgrilles.fr, i checked in operations-portal.in2p3.fr but i only found the registration url.
I also check the site https://cic.gridops.org/ but is not working.

Thanks in advance


Replies (3)

RE: producing a proxy - Added by Reynaud Sylvain over 12 years ago

Hello Jose,

About question 1 : the prompt is not part of JSAGA API, this code serves as a code example/command line to start with JSAGA (http://grid.in2p3.fr/software/jsaga-dev/jsaga-engine/xref/fr/in2p3/jsaga/command/ContextInit.html#72). This code example takes the user input to set the "UserPass" attribute of a context. In the case of a VOMS proxy, the "UserPass" attribute corresponds to the passphrase that protect your X509 certificate.

About question 2 : operations-portal.in2p3.fr does not provide the URL for "Server" attribute, but it provides the information needed to build it. I have just added a new section about this in VOMS adaptor FAQ : http://grid.in2p3.fr/software/jsaga-dev/adaptors/jsaga-adaptor-voms/faq.html#url. https://cic.gridops.org/ will be decommissioned and it is not supposed to be used anymore.

Both "UserPass" and "Server" attributes are required to generate a VOMS proxy.

Cheers,
Sylvain

RE: producing a proxy - Added by Saray Jose over 12 years ago

Thank you,
I correct the file according to your remarks and I have two more questions :

1) I launch the command sh jsaga-context-init.sh VOMS to generate the proxy and the program finishes with no output shown , that means the proxy was propertly created ? I check my filesystem and I did not see any generated proxy, is this normal ?

2) I am trying to execute the example NamespaceCopy with source url : file:/Documents/josefrancisco/comanditos target lfc:/grid/vo.rhone-alpes.idgrilles.fr/tidraone/ and the following error appears :

Exception in thread "main" NoSuccess: Found no data adaptor supporting scheme: file
at fr.in2p3.jsaga.engine.descriptors.DataAdaptorDescriptor.getClass(DataAdaptorDescriptor.java:69)
at fr.in2p3.jsaga.engine.factories.DataAdaptorFactory.getDataAdaptorAndConnect(DataAdaptorFactory.java:80)
at fr.in2p3.jsaga.impl.namespace.AbstractSyncNSFactoryImpl.doCreateNSFileSync(AbstractSyncNSFactoryImpl.java:77)
at fr.in2p3.jsaga.impl.namespace.AbstractSyncNSFactoryImpl.doCreateNSEntrySync(AbstractSyncNSFactoryImpl.java:51)
at fr.in2p3.jsaga.impl.namespace.NSFactoryImpl.doCreateNSEntry(NSFactoryImpl.java:35)
at org.ogf.saga.namespace.NSFactory.createNSEntry(NSFactory.java:222)
at org.ogf.saga.namespace.NSFactory.createNSEntry(NSFactory.java:161)
at fr.in2p3.jsaga.command.NamespaceCopy.main(NamespaceCopy.java:50)
Any clues?

RE: producing a proxy - Added by Reynaud Sylvain over 12 years ago

You're welcome.

About question 1 : no output shown means there was no error. If you have configured JSAGA to generate a proxy, then no error should means the proxy was properly created... If you can not find it, try fixing its location with attribute UserProxy, or look at its default location with command line "jsaga-help -s default".

About question 2 : adaptor for scheme "file" is defined in module jsaga-adaptor-classic.jar, is this module present in your classpath ?

Once this problem will be solved, you should get the following exception because excepted scheme for LFC is "lfn" :

Exception in thread "main" NoSuccess: Found no data adaptor supporting scheme: lfc

And finally, you should get the following exception because you can not put a physical file into a logical file repository :

Exception in thread "main" BadParameter: Not a physical file URL: lfn:/grid/vo.rhone-alpes.idgrilles.fr/tidraone/comanditos

What you want to do is probably to register your physical file into LFC with command "jsaga-logical-location", but since LFC does not allow for registring local files, you will have to copy it to SRM before registring it.

Cheers,
Sylvain

    (1-3/3)