Sorry, forgot how to use
this new mechanism in order to get a
proxy for a specific VO J
This (untested) code
should in principle work:
VomsProxyDescription
description = new VomsProxyDescription();
description.setVos(
listOfVOsIncludedInTheRequestedProxy );
AuthTokenRequest request
= new AuthTokenRequest( description, “gLite Job Submission”, “No
token found to submit a gLite job properly” );
IAuthenticationToken token
= AbstractAuthTokenProvider.staticRequestToken( request );
The listOfVOsIncludedInTheRequestedProxy
can for instance
contain the VO of the project for which a job is going to be submitted.
Cheers, Mathias
Von:
geclipse-dev-bounces@xxxxxxxxxxx [mailto:geclipse-dev-bounces@xxxxxxxxxxx] Im Auftrag von Stuempert, Mathias IWR
Gesendet: Montag, 10. Dezember
2007 17:14
An: Developer
mailing list
Betreff: [geclipse-dev] Changes in authentication token providers
Hi All,
Due to bug item #193935 I had to incorporate some changes to the core. This bug item requested the possibility
of requesting authentication tokens for a specific VO. Therefore several changes took place. To give you a rough overview:
1) IAuthenticationTokenDescription
has a new method matches( IAuthenticationTokenDescription ) that matches one
description against another
2) IVirtualOrganizations have now to properly implement equals(
Object )
3) IAuthTokenProvider#requestToken(
IAuthenticationTokenDescription ) was replaced by
IAuthTokenProvider#requestToken( AuthTokenRequest )
4) AuthTokenRequest
let you specify an
IAuthenticationTokenDescription, a requester as a String and
a purpose of the token as a String. The requester and
the purpose will be shown in the “No appropriate auth token found …
Should a new token be created …” dialog if present. This makes the
authentication process much more transparent
for the user. We can discuss about
the way these Strings are incorporated in the dialog, currently it is done in
the most simple way, the requester is taken as the dialog’s title and the purpose is taken as the message text.
5) The
AbstractAuthTokenProvider has a new method staticRequestToken( AuthTokenRequest
) that supports this mechanism. In
fact I plan to completely replace
staticRequestToken( IAuthenticationTokenDescription ) with the new method.
Therefore I ask you to check your code of occurrences of this method and to replace them with the new method!!!
This is a first shot implementation and may still contain bugs. It is therefore important that you now change
to this new mechanism and forget about the old one in order to test it and give me feedback. I will close #193935 since the
functionality is in principle there. So if you find any
bugs please report them in a separate item.
Thanks,
Mathias
