Auth API: OGR CARTO Driver and System tables

While using regular api-keys the OGR CARTO driver fails because it assumes access to the system tables in order to figure out column names and types of tables. Also, in order to handle SRS, it’ll hit spatial_ref_sys to dereference SRID numbers.

Regular API key should always have access to spatial_ref_sys and also have access to geometry_columns.

cc/ @rafatower & @pramsey

[pramsey]

Well, anyone using the GDAL/OGR driver is probably using it with the master key, and that still works, it’s just not something we want people to do anymore. So our desires (use restricted keys, don’t use master) are in conflict with our actions (using restricted keys actually doesn’t work for some clients).

[rafatower]

You’re right, but at the same time a feature that used to work does not anymore, and it slipped fairly unnoticed (and that makes me feel personally uncomfortable).

You know, the server(s) can be changed rather quickly on our side, but the patches for GDAL can take longer to actually reach users (because of packaging, dependencies, availability in different OS’s, etc).

There is something to learn from this, but I haven’t fully figured it out yet. Does nobody use GDAL CARTO driver? or don’t people reach out when they try and it fails?