Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Claims key: 'https://hasura.io/jwt/claims' not found

See original GitHub issue

i am getting following error:

"claims key: 'https://hasura.io/jwt/claims' not found"

Issue Analytics

State:
Created 4 years ago
Reactions:4
Comments:8 (2 by maintainers)

Top GitHub Comments

1reaction

markaucommented, May 16, 2021

For others stuck doing the Hasura tutorials: thanks @tonyjmartinez, I updated the Auth0 rule to apply the claims to the idToken as well, problem solved, i.e. I added

    context.idToken[namespace] =
    {
      'x-hasura-default-role': 'user',
      // do some custom logic to decide allowed roles
      'x-hasura-allowed-roles': ['user'],
      'x-hasura-user-id': user.user_id
    };

1reaction

keremgocencommented, Mar 21, 2021

@tonyjmartinez I have the same problem, were you able to resolve it?

Top Results From Across the Web

Ask Question - Stack Overflow

But I get this error message in the console, "Error: GraphQL error: claims key: 'https://hasura.io/jwt/claims' not found". Why? What could I ...

Authentication using JWT | Hasura GraphQL Docs

You can specify the key name, inside which the Hasura specific claims will be present, e.g. https://mydomain.com/claims . Default value is: https://hasura.io/ ...

Using JWTs for GraphQL Authorization with Hasura - Auth0

Learn how GraphQL APIs can be secured using JSON Web Tokens for authorization in the Hasura GraphQL Engine and CLI platform.

Hasura Authentication Explained - Medium

So that is not an actual authentication. ... This is used for some providers to expire a key. ... "https://hasura.io/jwt/claims": {

5.2 Protect GraphQL Endpoint with JWT

"message": "claims key: 'https://hasura.io/jwt/claims' not found". } ] } If we remember, we got the same error when we tried to decode the...