AW: AW: AW: [geclipse-dev] Token creation

["Stuempert, Mathias IWR" <mathias.stuempert@xxxxxxxxxx>]

> I for the moment I try to make it work the simple way. After that I'd 
> like to implement a code independent from the middleware
implementation, 
> then I think I should use of the AbstractTokenProvider.

Not necessarily but it would make things much easier.

> Using that code I still gets me the null pointer exception.

Ok, this is due to a bug in GlobusProxy#validate. I will fix this for
the next release. You can simply work around this by doing

proxy.validate( new NullProgressMonitor() );

instead of

proxy.validate( null );

> I have not mention any password for the certificates. I think I should

> provide it to geclipse, don't I ?

No, g-Eclipse guesses a PW from your login info at your local machine
and from the IDs of various hardware components installed in your local
computer, mixes it up with the current inclination angle of the earth,
the weight of your girlfriend, the name of the current favourite in the
US democrats pre-elections and throws it away afterwards ... of course
all your other (really used) passwords are cached and sent to
www.geclipse.eu :D

Sorry, of course this is my mistake, I have simply forgotten to mention
it ;-) So here is the piece of code that you have to insert before the
proxy creation:

PasswordManager.registerPassword( pwuid, pw );

The pwuid is a unique ID used by the proxy creation to query for the PW.
In the case of a globus proxy this is just the file path of your key
file, so in your case:

String pwuid = "/home/reuillon/.globus/userkey.pem";

And of course pw is the password itself (the keys passphrase, not the
g-Eclipse auto-generated one ;-). Note that g-Eclipse passwords are only
session-persistent. When restarting g-Eclipse or an application based on
it all formerly registered PWs are lost.

Cheers, Mathias