The only additional access required is VenueServer.GetVenues. Tom
Todd Zimmerman wrote: > Not sure if this is your issue - but I've just run into something very > similar - it was caused by our bridgeserver certificate not being > authorized to connect to the venueserver (two different machines - two > different certificates). > > I added the bridgeserver DN to the venueserver administrators list and > it worked after that. > > Giving administrator access is a bit extreme, obviously - and I'd like > to narrow the scope of authorization; however, I wasn't sure which > 'Actions' the bridgeserver was required to be authorized for. Any > advice from other admins would be great! > > Todd > > -- > Collaboration & Visualization Technician > WestGrid - www.westgrid.ca > IRMACS - www.irmacs.com > Ph. 604.268.6979 > Todd Zimmerman - to...@sfu.ca > > > > Socrates wrote: > >> Hi, >> >> I'm trying to run a bridge on my local server but it doesn't seem to >> work. >> I start the BridgeServer.py script with a config file containing the >> URI of the server (want all Venues bridged). I start the Client on >> another machine but the "unicast" option in the menu is still grayed >> out. >> >> WiKi says that the Lucky Labrador Venue is bridged by Argonne: >> ( >> http://www-unix.mcs.anl.gov/fl/research/accessgrid/wiki/moin.cgi/BridgedVenues >> >> >> ) >> >> Starting my Client on that room doesn't enable "unicast" on the menu >> either. >> >> Any ideas? This is all Fedora Core 3. No errors reported in >> BridgeServer.log, VenueServer.log or VenueClient.log. >> >> Thanks, > > >
