On Thu, Jan 29, 2009 at 12:09 PM, Jan Muhammad <[email protected]> wrote: > > I download the source > (http://workspace.globus.org/downloads/globus_voms_interceptors_0.2.tar.gz), > build the gar and deployed to container successfully. > > 1. But after deploying the service I don't see any additional service in the > container after deploying.
We (Globus) don't distribute a VOMS service (if that's what you're looking for). For that you need to explore the links that Alan posted earlier. The VOMS incubator project supports a pair of VOMS interceptors for the Globus container. These interceptors are *consumers* of VOMS attribute certificates. > 2. If you look at that document Configuration section, its not clear which > service's security-config.xml file to edit > (http://dev.globus.org/wiki/Incubator/VOMS/Installing#Configuring_the_authorization_chain) Well, you apply those configuration changes to whatever service you want to "VOMS-enable." In principle, any service running in the Java WS Core container will do. > I will assume that it is talking about the service that I want to protect. Correct. > 3. Then at the "Setting Configuration parameters section" it has not > mentioned about PIP configuration parameters and PDP configuration > parameters that where and in which files these will go? That depends on the GT version you're running (technically, only Java WS Core is required). In theory, the VOMS interceptors work with both 4.0 and 4.2, but I suspect you'll have trouble with 4.2 initially. Others have reported problems with the latest versions of GT 4.2, unfortunately. http://bugzilla.globus.org/globus/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=VOMS&content= So I think the first thing you should do (if it doesn't say this in the documentation, it should) is read the documentation regarding the authorization framework for the version of GT you're interested in. Tom
