[Dachs-support] Restricting adql

Mariangeles Mendoza ninesmp75 at gmail.com
Thu Feb 3 11:03:32 CET 2022


Thanks for the quick response.
The Dachs-support team is extremely helpful and efficient :P

Cheers,
Maria Angeles



On Thu, Feb 3, 2022 at 10:50 AM Markus Demleitner <
msdemlei at ari.uni-heidelberg.de> wrote:

> Hi Maria,
>
> On Thu, Feb 03, 2022 at 08:55:14AM +0100, Mariangeles Mendoza wrote:
> > I am trying to restrict access by adql.
> > For it I have saved an empty adql.rd in
> > /var/gavo/inputs/__system
> > following the instructions of:
> >
> http://docs.g-vo.org/DaCHS/howDoI.html#protect-my-tap-service-against-usage
> >
> > However, it doesn't work either. what am I doing wrong?
>
> Argl.  Having a __system directory in inputs really was a bad move
> when I made it.  I'll look into moving this somewhere else, because
> this is not the first time this confuses people.
>
> The directory you need to put overridden system RDs into is
> /var/gavo/inputs/__system__ (note the trailing underscores).  Sorry
> about this.
>
> Incidentally, just putting an empty file in there gives an ugly error
> message; it's perhaps smarter to
>
> mkdir -p /var/gavo/inputs/__system__
> cd /var/gavo/inputs/__system__
> dachs adm dumpDF //adql > adql.rd
>
> and then edit adql.rd such that
>
>         <service id="query" core="qcore">
>
> becomes
>
>         <service id="query" core="qcore" limitTo="tapusers">
>
> (or whomever you want to limit access to) -- that way, people with
> the necessary credentials can still do ADQL queries from the web.
>
> Sorry about the confusion; I'll add a note to the docs.
>
>           -- Markus
> --
> Dachs-support mailing list
> Dachs-support at g-vo.org
> https://lists.g-vo.org/mailman/listinfo/dachs-support
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.g-vo.org/pipermail/dachs-support/attachments/20220203/3500f19c/attachment.htm>


More information about the Dachs-support mailing list