Page MenuHomePhabricator

Lock down public Blazegraph instance
Closed, ResolvedPublic

Description

Blazegraph allows new triples to be added through its :9999 interface, which is sadface for hosting a public instance. This epic is here to capture the various security issues blocking a public-facing release of WDQS.

At a minimum, the public will need:

  • POST access to :9999/bigdata/namespace/<namespace>/sparql to submit SPARQL queries.
    • Can we restrict SPARQL queries that lead to inserts/updates/deletes?

Event Timeline

Jdouglas raised the priority of this task from to Medium.
Jdouglas updated the task description. (Show Details)
Jdouglas subscribed.

Why would they need POST access? POST is used for update queries. I don't think we should allow public to update. The regular queries go through GET interface.

Smalyshev claimed this task.

I think this is done, Blazegraph only listens to localhost:9999 now and nginx proxy does not allow POST to pass to it.