The wikidata query service defines a whitelist to search for allowed SPARQL hosts. We use WDQS to manage mathematical research data. In this context, the term whitelist is discouraged. An alternative is allowlist.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | RKemper | T343856 Move whitelist.txt from WDQS deploy repo into puppet and rename it to "allow list" | |||
| Resolved | BUG REPORT | RickiJay-WMDE | T355893 Rename WDQS whitelist to allowlist |
Event Timeline
Comment Actions
I stumbled over this when looking into a problem reported by @Daniel_Mietchen, who realized that the values in the allow-list do not seem to work https://github.com/MaRDI4NFDI/portal-compose/issues/473. So maybe this is also the cause of a functional problem.
Comment Actions
According to https://gerrit.wikimedia.org/r/c/wikidata/query/rdf/+/949102/2/dist/src/script/runBlazegraph.sh#8 whitelist.txt should still be used.
Comment Actions
According to the manual it should also be whitelist https://www.mediawiki.org/wiki/Wikidata_Query_Service/User_Manual#Configurable_properties
Comment Actions
However, on the box we use I see the following
bash-4.4# cat runBlazegraph.sh | grep allow
ALLOWLIST=${ALLOWLIST:-"allowlist.txt"}Comment Actions
We've been getting reports of Wikibase community WDQS end-users having trouble using whitelist.txt - might the changes in T343856 have broken use of this file if they had it incorporated into a Wikibase docker/suite setup? It looks like wmde.16 version of wikibase-release-pipeline is still using whitelist.txt.
Example from the Wikibase Community telegram chat:
"this should work, but you’ll need to allow WDQS in your query service’s allowlist first [...] no, it’s usually a file whitelist.txt in your WDQS installation"
"weird. I'm on a default installation of wikibase from docker, and that default installation contains the wikidata query service in its whitelist.txt So why is it not allowed...? hmm..."
(I think the plan for MediaWiki: spam message changes had allow/deny variants as additions to existing white/black rather than replacing them, at least for a transition period. It seems there is backwards-compatibility code in T344284 that anticipates this, but maybe it is not working as intended?)
Comment Actions
For our project, we solved it by overwriting the name https://github.com/MaRDI4NFDI/portal-compose/commit/f10c191a7899a43b4c68e0ec8ee986460fefb65d . Would it be helpful to back-propagate this fix to https://github.com/wmde/wikibase-release-pipeline/blob/main/example/docker-compose.extra.yml ? If so, I can make a pull request.