Skip to content

v1.1.0

Latest

Choose a tag to compare

@ThHanke ThHanke released this 20 Mar 08:30

What's new

CKAN-authenticated SPARQL proxy

All Fuseki dataset endpoints are now transparently proxied through CKAN at /dataset/{id}/fuseki/$/{path}, enforcing CKAN's own access control:

Public datasets are accessible to anyone via the proxy

Private datasets require CKAN authentication (browser session or API token via Authorization header)
Write operations (SPARQL UPDATE, graph store writes, file upload) additionally require package_update permission
Direct anonymous access to Fuseki is blocked at the Fuseki level
Embedded YASGUI query interface
A built-in YASGUI editor is now served at the "Query Dataset" button when no Sparklis URL is configured — no external dependency needed for interactive SPARQL queries.

Config-only settings

All previously environment-variable-based settings (FUSEKI_SSL_VERIFY, FUSEKI_CKAN_TOKEN, etc.) are now declared as proper ckanext.fuseki.* CKAN config options, fully compatible with CKANINI__ Docker environment variable injection.

Access information panel

The Fuseki tab now shows an access information block with the dataset's SPARQL endpoint URL, authentication methods (browser session or API token), and named graph layout — visible in the screenshot above.

Custom Fuseki deployment

The optional/ folder provides a ready-to-use custom Fuseki image (Dockerfile + docker-entrypoint.sh) that blocks anonymous dataset access and fixes asset paths for subpath (nginx) deployments.

Breaking changes

SPARQL endpoint URLs changed from /fuseki/{id}/* → /dataset/{id}/fuseki/$/*
Requires the custom Fuseki deployment (see optional/ folder or SECURITY.md)

Full Changelog: v1.0.8...v1.1.0