Currently the fts-rest job listing lists jobs, filtering with various filters which can be specified in the request. The filters include state, dn and vo. Regarding authorisation:
if no state filter is given all non-finished jobs may be listed, subject to any dn or vo filter.
(ii) if the state filter is given only jobs in those states and belonging to the user are returned.
The c++ command line interface always gives a list of states.
Conversely the behaviour of the gsoap based job listing may be different: for the gsoap requests, the roles section of /etc/fts3/fts3config is consulted. The user may be able to list only their own job, or all jobs within their vo, or all jobs. On the development instance, by default with no specific role, one can list all jobs within the vo.
Is the tighter limitation ok for the rest based listing?