Authenticated request with custom check on X-Hasura-User-ID not working

[valentin-harrang]

Hi,

I trying to do an authenticated request with custom check on X-Hasura-User-ID from Next.js App:

I get a 200 status from Network tab of DevTools after executing my mutation:

Mutation :

const LOVE_MUTATION = gql`
  mutation insert_loved_language($objects: [loved_language_insert_input!]!) {
    insert_loved_language(objects: $objects) {
      affected_rows
    }
  }
`;

const [love, { loading }] = useMutation(LOVE_MUTATION, {
    variables: {
      objects: {
        name: "Typescript",
      },
    },
  });

But I get this error:

{"errors":[{"extensions":{"code":"validation-failed","path":"$.selectionSet.insert_loved_language.args.objects[0].name"},"message":"field 'name' not found in type: 'loved_language_insert_input'"}]}

Yet the name field does exist and the X-Hasura-User-Id is passed in the payload of my jwt.

JWT:

jwt {
  sub: 'K0RmvMupciVEiJVwhikj',
  name: 'Valentin',
  email: '[email protected]',
  iat: 1669105034.515,
  exp: 1669191434,
  'https://hasura.io/jwt/claims': {
    'x-hasura-allowed-roles': [ 'user' ],
    'x-hasura-default-role': 'user',
    'x-hasura-role': 'user',
    'x-hasura-user-id': 'K0RmvMupciVEiJVwhikj'
  }
}

The mutation works using the Hasura console with the x-hasura-admin-secret but not with x-hasura-user-id:

I don't know why I have this error, do you have any idea how to fix it? 🙏

[meetzaveri]

Hey @valentin-harrang

Thanks for asking.

Since loved_language_insert_input schema is object wrapped around array structure, you'll need to pass like

objects: [ 
      // inside array structure
      {
          name: "Typescript",     // pass your actual object that you want to insert  (which matches schema)
      }
]

Please let me know if that doesn't work for you!

UPDATE (post-solved):
When you add column preset for column, then while performing insert mutation if you are passing value to that field via query variables, it will only accept the value which had been set in column preset. Hence, introspection query in graphiQL will show you validation failed error because that column has already been added in column preset in INSERT permission for that specific role (in this case user)

If you intend to pass value to that field from insert mutation, then please remove that column from Column presets.

[valentin-harrang]

The select query works:

[meetzaveri]

@valentin-harrang
This error that you are getting in insert operation is due to the reason being you have your column preset of name already applied with static value. If you remove that, then mutation will take the value from the query variables.

Can you try removing column preset for name column ? then it will accept input from query variables in insert operation.

[valentin-harrang]

@meetzaveri I can't because when I remove the column, the Save Permissions button is disabled

[meetzaveri]

Then please delete permissions and re-create it again with the solution mentioned above ( do not include name in column presets)

[valentin-harrang]

It works ! Thank you @meetzaveri :)