Hi Again,
I was just able to create,
validate and activate a VOMS proxy for the gridats VO, so for me the problem
seems to be solved. Thanks for giving me access to your VO. Would be great if
you could report back your experience with the nightly build tomorrow.
Cheers, Mathias
Von: Alessio Curri [mailto:alessio.curri@xxxxxxxxxxxxxxxxxx]
Gesendet: Montag, 26. Mai 2008
14:19
An: Stuempert, Mathias IWR
Cc: Developer mailing list
Betreff: Re: AW: AW:
[geclipse-dev] [Fwd: gEclipse - voms proxy creation exception]
Hi,
first of all, many tnx for the really fast answer!
tomorrow i will download and try the nightly build and in the meantime i can
gran you the access to the vo.
to register, pls go to the https://voms01.grid.elettra.trieste.it:8443/voms/gridats/
page
Grazie,
Alessio
Stuempert, Mathias IWR wrote:
Hi Alessio,
Looking at the VOMS code
it seems they actually changed their VOMS protocol to contain a new version
tag. I changed our VOMS protocol parser in order to accept this tag and
furthermore to not stop for unknown tags but to only log them. So when trying
either from HEAD or with our nightly build of tomorrow you should already get
the new code. Nevertheless our next milestone release is foreseen for end of
this/beginning of next week.
Of course I cannot test
things now for your VO since I am not a member of this VO. So either you grant
me temporary access or you’ll have a try by yourself, up to you.
Nevertheless at least I now get the error I am getting for any VO I am not a
member of :)
Hope that helps,
Mathias
Von: Alessio Curri [mailto:alessio.curri@xxxxxxxxxxxxxxxxxx]
Gesendet: Montag, 26. Mai 2008
12:43
An: Developer mailing list
Cc: Stuempert, Mathias IWR
Betreff: Re: AW: [geclipse-dev]
[Fwd: gEclipse - voms proxy creation exception]
Some more information about the voms server:
it runs Scientific Linux CERN SLC release 4.6 (Beryllium)
the voms server was installed using the GLite 3.1, using the
ig_VOMS_mysql-3.1.8-0_ig16_sl4 metapackage (which requires
glite-VOMS_mysql-3.1.10-0)
If you need access to the vo for test, i can provide it
Alessio
Stuempert, Mathias IWR wrote:
Hi,
Just had a test with the specified VO information. I get:
eu.geclipse.core.reporting.ProblemException: Invalid node name: version
at eu.geclipse.voms.server.VomsServerResponse.parseVomsans(VomsServerResponse.java:231)
at eu.geclipse.voms.server.VomsServerResponse.parseResponse(VomsServerResponse.java:189)
at eu.geclipse.voms.server.VomsServerResponse.<init>(VomsServerResponse.java:69)
at eu.geclipse.voms.server.VomsServerResponse.read(VomsServerResponse.java:75)
at eu.geclipse.voms.server.VomsServer.query(VomsServer.java:178)
at eu.geclipse.voms.auth.VomsProxy.setActive(VomsProxy.java:171)
at eu.geclipse.ui.views.AuthTokenView$6.run(AuthTokenView.java:528)
at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:369)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:313)
at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:495)
at eu.geclipse.ui.views.AuthTokenView.setSelectedTokenActive(AuthTokenView.java:525)
at eu.geclipse.ui.views.AuthTokenView$10.run(AuthTokenView.java:701)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:545)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:490)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:402)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:153)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:504)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:443)
at org.eclipse.equinox.launcher.Main.run(Main.java:1169)
at org.eclipse.equinox.launcher.Main.main(Main.java:1144)
which implies that the VOMS server somehow returns an answer that is not compliant with the supported answer format of g-Eclipse. The returned XML contains a tag called <version> which was not specified in the VOMS protocol we implemented. So for me it would be very interesting to know which VOMS version the server runs.
For reference, the full answer looks like this:
<?xml version="1.0" encoding = "US-ASCII"?><vomsans><version>3</version><error><item><number>1001</number><message>gridats: Unable to satisfy Request!</message></item></error><ac>qq</ac></vomsans>
Ariel, did they change the VOMS protocol for gLite or may this be an artefact of an older version? In any case I will try to include this in our protocol parser as soon as I can find a documentation for this, but as we know this may end up in reverse engineering the VOMS server code.
Cheers, Mathias
-----Ursprüngliche Nachricht-----
Von: geclipse-dev-bounces@xxxxxxxxxxx [mailto:geclipse-dev-bounces@xxxxxxxxxxx] Im Auftrag von Mateusz Pabis'
Gesendet: Montag, 26. Mai 2008 11:02
An: Developer mailing list
Cc: Alessio Curri
Betreff: [geclipse-dev] [Fwd: gEclipse - voms proxy creation exception]
Hi,
We had this problem in Triest last week, I couldn't find a solution by
myself, so I'm forwarding it here. Any ideas what's wrong?
----------------------------------------------------------------------
Hi,
i'm using the last version i found in the gEclipse website on a MacOSX
10.4 (intel)
when i try to create a voms proxy i receive this exception:
eu.geclipse.core.GridException: Syntax error in VOMS server response
at eu.geclipse.voms.server.VomsServerResponse.parseVomsans(Unknown
Source)
at eu.geclipse.voms.server.VomsServerResponse.parseResponse(Unknown
Source)
at eu.geclipse.voms.server.VomsServerResponse.<init>(Unknown Source)
at eu.geclipse.voms.server.VomsServerResponse.read(Unknown Source)
at eu.geclipse.voms.server.VomsServer.query(Unknown Source)
at eu.geclipse.voms.auth.VomsProxy.setActive(Unknown Source)
at eu.geclipse.ui.views.AuthTokenView$6.run(Unknown Source)
at
org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:369)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:313)
at
org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:495)
at eu.geclipse.ui.views.AuthTokenView.setSelectedTokenActive(Unknown
Source)
at eu.geclipse.ui.views.AuthTokenView$10.run(Unknown Source)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
at
org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:546)
at
org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:490)
at
org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:443)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1495)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1519)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1504)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1295)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3350)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2954)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
at
org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at
org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:169)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:508)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447)
at org.eclipse.equinox.launcher.Main.run(Main.java:1173)
eclipse.buildId=M20071023-1652
java.version=1.5.0_13
java.vendor=Apple Computer, Inc.
BootLoader constants: OS=macosx, ARCH=x86, WS=carbon, NL=en_US
Framework arguments: -keyring /Users/alessio/.eclipse_keyring -showlocation
Command-line arguments: -os macosx -ws carbon -arch x86 -keyring
/Users/alessio/.eclipse_keyring -consoleLog -showlocation
i'm using a voms vo called "gridats"(the VOMSES string for this VO is
"gridats" "voms01.grid.elettra.trieste.it" "15000"
"/C=IT/O=INFN/OU=Host/L=Elettra/CN=voms01.grid.elettra.trieste.it"
"gridats")
If i use a standard UI, the voms proxy creation works fine.
I've imported all the CA...
Tnx for the support ;)
Alessio
--
Alessio Curri
+39 040 375 8064
Software for Measurement Group
Experiments Division
Sincrotrone Trieste S.c.p.A.
S.S. 14 Km 163.5, in Area Science Park
34012 Basovizza - Trieste (Italy)
--
Alessio Curri
+39 040 375 8064
Software for Measurement Group
Experiments Division
Sincrotrone Trieste S.c.p.A.
S.S. 14 Km 163.5, in Area Science Park
34012 Basovizza - Trieste (Italy)