No mutation operation access is allowed on remote schema for unauthenticated users after running hasura metadata apply
See original GitHub issueVersion Information
Server Version: 2.6.0 CLI Version (for CLI related issue): >= 2.5.0
Environment
OSS
What is the expected behaviour?
Unauthenticated users should always be able to access mutation operation provided by the remote schema that enabled public insert/update mutation
Keywords
mutation remote schema unauthenticated users hasura metadata apply
What is the current behaviour?
After running hasura metadata apply, all public access to mutation operation on any remote schema that enabled public insert/update mutation is resulting in an error field not found in type: 'mutation_root'
or mutation not exists
How to reproduce the issue?
- Allow insert/update from unauthenticated users on a remote schema using web console
- Export metadata to the local Hasura console
- Reapply metadata from the local Hasura console
Any possible solutions?
Modify any permission on the same remote schema again using web console.
After comparing the metadata of remote schema before and after I did the above solution, I found the difference is the missing schema { query: Query mutation: Mutation }
in the permission definition schema makes it not work.
Can you identify the location in the source code where the problem exists?
No
If the bug is confirmed, would you be willing to submit a PR?
I am not familiar with Go or Haskell
Issue Analytics
- State:
- Created a year ago
- Comments:23 (7 by maintainers)
@maxcan @AThilenius Re-opening this till we get more information. cc: @BenoitRanque @birlam
I found that issue happens not only to the unauthenticated users but also all other roles