Repository navigation
Description
Is there an existing issue for this?
- I have searched the existing issues
Current Behavior
When testing API-token allow-lists, a token whose allow-list names a specific template (template:<template-uuid>) gets an HTTP 500 from any request that runs the authorized templates query. Workspace creation with the same token succeeds. Reading the workspace back afterwards fails, because building the workspace response loads templates through GetAuthorizedTemplates.
The same token with template:* instead works.
Relevant Log Output
GET /api/v2/workspaces/<workspace-id>
500 {"message":"Internal error fetching workspace resources.","detail":"get templates: pq: column reference \"id\" is ambiguous"}Expected Behavior
Requests for templates named in the token's allow-list are authorized normally (here, GET /api/v2/workspaces/<workspace-id> returns 200), and templates outside the allow-list are filtered out.
Steps to Reproduce
- As an admin, create a regular user
<user>with the default Member role in the default organization. - Create a scoped token for that user with a template-specific allow-list:
coder tokens create --user <user> --lifetime 1d \ --scope coder:workspaces.create --scope coder:workspaces.access \ --allow template:<template-uuid> \ --allow workspace:* \ --allow organization_member:<user-uuid> - With that token,
POST /api/v2/users/<user>/workspacesusing a version of<template-uuid>. This returns 201. - With that token,
GET /api/v2/workspaces/<workspace-id>. This returns the 500 above. - Repeat with
--allow template:*instead of--allow template:<template-uuid>. Step 4 then returns 200.
Root cause
TemplateConverter() in coderd/rbac/regosql/configs.go registers resourceIDMatcher(), which emits an unqualified column:
func resourceIDMatcher() sqltypes.VariableMatcher {
return sqltypes.StringVarMatcher("id :: text", []string{"input", "object", "id"})
}GetAuthorizedTemplates in coderd/database/modelqueries.go appends the compiled filter to GetTemplatesWithFilter, which joins a second table that also has an id column:
SELECT t.*
FROM template_with_names AS t
LEFT JOIN template_versions tv ON t.active_version_id = tv.id
WHERE ...The ID predicate is only emitted when the allow-list names a specific template ID. That is why wildcard allow-lists, and tokens without allow-lists, are not affected. The same converter already qualifies the organization column (t.organization_id :: text), so the likely fix is a template-qualified ID matcher in TemplateConverter, such as t.id :: text. A regression test that compiles a non-wildcard template allow-list against this query would cover it.
Workaround
Use --allow template:*. The token can then read and use any template the user's role can already access, so pinning to one template has to be enforced by the client.
Environment
- Host OS: macOS (arm64), Coder server with built-in PostgreSQL
- Coder version: v2.38.7. The same code is present in v2.39.1 and on
mainat 1126533 (resourceIDMatcherandTemplateConverterincoderd/rbac/regosql/configs.go,GetTemplatesWithFilterincoderd/database/queries/templates.sql).
Additional Context
The issue occurs consistently. Possibly related to the broader compiled-SQL audit in #25982, but this is a specific query failure rather than an ACL semantics difference.
Activity
linear-code commentedon Nov 11, 2026
ENG-3532
simonepri commentedon Nov 13, 2026
Hit this too with a narrower token:
--scope workspace:read --scope template:read --scope user:read --allow template:<uuid>(plus workspace/user allow entries). BesidesGET /api/v2/workspaces/<id>,GET /api/v2/users/me/workspace/<name>fails with the samecolumn reference "id" is ambiguous.template:*works around it for us too.