Mutation returns null in data

Issues GraphQL
, , ,
1

Hello,
I have set Auth with JWT. For now only with ## Dgraph.Authorization.
When performing mutation with invalid jwt mutation I receive:

"data": {
        "addPerson": null
    },

and with many transactions:

"errors": [
        {
            "message": "Mutation addOrganization was not executed because of a previous error.",
            "locations": [
                {
                    "line": 10,
                    "column": 10
                }
            ]
        }
    ],
    "data": {
        "addPerson": null
    },

Can you explain to me why it does not return error like query does?
F.e:

"errors": [
        {
            "message": "couldn't rewrite query queryPerson because unable to parse jwt token:token is expired by 13h48m9.195314817s"
        }
    ],
    "data": {
        "queryPerson": []
    },

or for many transactions:

"errors": [
        {
            "message": "couldn't rewrite query queryPerson because unable to parse jwt token:token signature is invalid"
        },
        {
            "message": "couldn't rewrite query queryOrganization because unable to parse jwt token:token signature is invalid"
        }
    ],
    "data": {
        "queryPerson": [],
        "queryOrganization": []
    },

I know that transactions in mutation are done one by one that is why second is interrupted.
I want to know why tere is no error about auth in mutation.

1 Like
2

Hi @Shohoo, yeah currently we hide all the auth errors from the mutation. That was done to hide any information leak. But that is not correct behaviour like in jwt related errors.
We will change that behaviour soon.

2 Likes