[Dachs-support] UWS and user access control
Ivan Zolotukhin
ivan.zolotukhin at gmail.com
Mon May 9 12:07:20 CEST 2016
On Fri, May 6, 2016 at 11:41 AM, Markus Demleitner
<msdemlei at ari.uni-heidelberg.de> wrote:
> Hi Ivan,
>
> On Wed, May 04, 2016 at 03:50:27PM +0200, Ivan Zolotukhin wrote:
>> I'm also having issues with uws-client as it does not handle HTTP
>> redirects and therefore simply fails when accessing job through the
>> incorrect URL (which belongs to another UWS) or even posting to it
>> (e.g. to delete a job). Probably it's easy to fix by telling urllib2
>> to follow redirects, but this problem anyway is related to our
>> separate discussion on exposing jobclass in the list of jobs, see
>> below.
>
> I *think* I'm completely within UWS with my 303s in these cases, and
> I think I've seen a fix for uwsclient already.
>
>> >> Therefore, the minimal thing from DaCHS for me would be actually
>> >> exposing jobclass and job owner properties in the list of jobs --
>> >> ideally in a way which is compatible to access through the python-uws
>> >> client.
>>
>> > The list of jobs has a fairly strict format, and there's no way to
>> > have user, let alone jobclass, without resorting to dirty tricks.
>>
>> > But perhaps the per-user joblists already do the trick for you?
>>
>> > As to the job classes, there are a couple of ways out, and lacking a
>> > use case of my own I cannot really say where I should go.
> [...]
>>
>> > (b) I could, in each UWS, just list the jobs submitted by it. This
>> > loses the queue perspective, but perhaps that's a silly argument in the
>> > first place. Advantage: clean on the code side.
>>
> [...]
>>
>> Now I am sure that I can't live without understanding which job
>> belongs to which service looking on the list of jobs. I do not mind
>> which way you prefer, a,b or c. For me b) which you seem to like also
>> looks fine. I won't repeat my previous arguments, I'd just add that by
>> implementing this one would avoid hacking uws-client as there will be
>> no more need to look for job properties using the incorrect URL
>> belonging to another UWS.
>
> Ok -- I've implemented (b) in svn rev. 5032.
>
> Is that good enough for you?
Works like magic, thanks!
More information about the Dachs-support
mailing list