On Fri, 22 Aug 2008 11:20:09 +0200, dejw wrote: > Hi, > Thomas Leonard wrote: >> Hi Dawid, >> >> One way to handle this is to have the broker create the job as itself >> and then transfer ownership to the client. Then the broker does not >> need any special privileges. >> > Could you explain me what do you mean in case of "transfer ownership"? > If broker submits the job > then broker is the owner of this job in GRIA. And as I understand the > broker is able to move the > ownership to someone else who is trusted GRIA user? Then all information > connected with such job (and all data stagers) will change the ownership > to other user (pointed by the broker?).
Yes, but there are no "trusted" users. The broker can delegate to anyone it wants to, by providing their CA certificate and DN. For self-signed certificates, the CA is just the user's certificate, of course. To do this, the broker will do: job = ... // create new job job.addPolicyRule(new PolicyRule(theUser, "owner")); job.removePolicyRule(new PolicyRule(broker, "owner")); You can transfer the inputs and outputs in the same way (using the "manager" role). This allows you to create jobs where different people provide different inputs and receive different outputs. I will let someone else answer the registry query. -- Dr Thomas Leonard IT Innovation Centre 2 Venture Road Southampton Hampshire SO16 7NP Tel: +44 0 23 8076 0834 Fax: +44 0 23 8076 0833 mailto:[EMAIL PROTECTED] http://www.it-innovation.soton.ac.uk ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ gria-general mailing list gria-general@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gria-general
