I’m not sure if this is intentional, but when the query part does not allow the retrieval of an object, graphql errors are being masked. Schema: type Foo @auth( query: { rule: "{$DENIED: { eq: \"DENIED\" } }" } ) { username: String! @id } Steps to reproduce: Add Foo mutation { addF…

Query auth-rules mask graphql error propagation

amaster507 (Anthony Master) April 6, 2021, 2:36pm 2

1 Like

Topic		Replies	Views
Restrict visibility of graphql mutation and queries GraphQL	4	845	July 30, 2020
Mutation returns null in data GraphQL kind:question , status:accepted , kind:bug , ticket:created	1	1232	April 29, 2021
Resolving updateGQLSchema failed because Type User: @auth: failed to validate GraphQL rule [reason : Field "eq" is not defined by type ID.] Dgraph Cloud	1	1113	April 1, 2022
Allow users to only see themselves (@auth) GraphQL status:accepted , kind:bug , ticket:created	9	663	September 20, 2021
RBAC Delete Mutation Throws Error When Used Without JWT GraphQL auth , kind:bug , area:mutations	2	629	September 28, 2020