Geodata reads limited to the visible catalogue (B3, B4)
OrionAI 2.46.0Released 9 November 2026
Table-based operations (select zones, point in polygon, buffers, aggregates) and hosted raster layers now run only against datasets the signed-in user can actually see: the web app resolves the visible catalogue with the user's own GeoNode token and Core validates every table and layer name against it, failing closed when the set can't be resolved.
Changes since 2.45.0.
#Security
- Table names are checked against the visible catalogue.
select_zones,point_in_polygon,buffer_intersectanddissolve_aggregatepreviously accepted any table name in the geodata store, so a crafted request could read tables the caller had no permission for. The web app now resolves the caller's visible datasets with their own GeoNode token (GeoNode's permission rules decide) and passes the set into the analysis; Core rejects any table name outside it, and fails closed if the set is absent. - Hosted raster layers are checked the same way. A
hosted:raster reference now must be in the caller's visible catalogue before Core builds the WCS read; without a resolved set the step refuses rather than reading unauthenticated. - The plan prompt lists the visible tables, so the AI picks real, permitted table names instead of guessing.
#Notes
- Base rasters, index sources and earlier raster results are unaffected.
- Web-app plumbing for the same release ships in oriongis-web 1.55.2.