hasura / hasura/graphql-engine

Remote Schema Permissions: field not found in type query_root

Open
#6,892 5 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
32.1k
Forks
3k
PR merge metrics
PR metrics pending

Description

Using the latest `Hasura v2.0.0-alpha.10` and trying out Remote Schema Permissions. Test environment is docker-compose on Windows 10 using latest Docker Desktop for Windows.

We added a few remote schemas to services running `Hasura 1.3.2`, and configured permissions for a role named `visitor`. In this case, we only configured one permission for one query, `system_legacy_migration_logs` to a specific remote schema. All related types are also selected for that role.

When trying to issue a simple query, we receive an error as follows:

![image](https://user-images.githubusercontent.com/55542413/117670555-04d11280-b176-11eb-9a07-d7672ac909f2.png)

As you can see, we can select the query on the left, and it also shows up in the Docs, however the message seems to indicate that there is some permission issue? However as stated, all related types were automatically selected.

Do the remote schema services also need to run on `Hasura v2.0.0-alpha.10`? Is this a bug?

Also note that remote permissions work on public remote schemas not running Hasura (i.e. Apollo server).

Thanks

Contributor guide

Open the contributing guide

Research direction

The report names Hasura v2.0.0-alpha.10, Hasura 1.3.2, Docker Compose, and a remote schema using Apollo Server, but no repository file or test entry point. Start by reproducing the remote schema permission query with these versions and determine whether mixed Hasura versions cause the missing field. Done means the compatibility behavior or permission bug is confirmed and its resolution is captured in a regression test or clear issue guidance.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker-compose, graphql
Domain
api, authorization
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.