Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
AW: AW: [geclipse-dev] Changes in authentication token providers

Hi Harald,

According to the gLite's VOMS proxy definition it is possible to create a proxy for more than one VO. For instance

voms-proxy-init -voms geclipse -voms geclipsetutor

creates a proxy for both VOs geclipse and geclipsetutor. This functionality is also implemented for g-Eclipse. Therefore you are able to select multiple VOs in the VOMS proxy wizard. This is the reason why this method takes a list of VOs.

The rationale behind this is that our projects are bound to one VO but our authentication tokens are detached from this logic. Therefore an advanced user is able to create one token that serves all his projects rather than creating a new token whenever he/she wants to do something in another project.

Cheers, Mathias


-----Ursprüngliche Nachricht-----
Von: geclipse-dev-bounces@xxxxxxxxxxx [mailto:geclipse-dev-bounces@xxxxxxxxxxx] Im Auftrag von Harald Kornmayer
Gesendet: Montag, 10. Dezember 2007 17:57
An: Developer mailing list
Betreff: Re: AW: [geclipse-dev] Changes in authentication token providers

HI Mathias 


> 
> VomsProxyDescription description = new VomsProxyDescription();
> 
> description.setVos( listOfVOsIncludedInTheRequestedProxy );

Why do you implement here a list? Will it be possible to create ONE
Token for many VOs? 
What is the rationale behind this?? 


Harald 



_______________________________________________
geclipse-dev mailing list
geclipse-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/geclipse-dev


Back to the top