search

hasura / graphql-engine

Blazing fast, instant realtime GraphQL APIs on your DB with fine grained access control, also trigger webhooks on database events.
https://hasura.io
Apache License 2.0
31.08k stars 2.76k forks source link

Schema introspection query failed {"errors":[{"message":"Application update required"}]} #9040

Open davidpanic opened 1 year ago

davidpanic commented 1 year ago

Version Information

Server Version: v2.12.0

Environment

Docker, hasura/graphql-engine:v2.12.0

What is the current behaviour?

When I try to use an authorization header in the console and click the "Decode JWT" button I get redirected to an error page with the below error. The console also complains: Schema introspection query failed {"errors":[{"message":"Application update required"}]} Nothing of use is printed to the container logs.

What is the expected behaviour?

To be able to use the console without the X-Hasura-Admin-Secret header to test queries as a user.

How to reproduce the issue?

  1. Uncheck the checkbox next to the X-Hasura-Admin-Secret header
  2. Add an Authorization header with the value Bearer [valid JWT here]
  3. Click the Decode JWT button on the right

Screenshots or Screencast

image image image image

Please provide any traces or logs that could help here.

e@https://graphql-engine-cdn.hasura.io/console/assets/channel/stable/v2.12/vendor.js.gz:1:2119848
e@https://graphql-engine-cdn.hasura.io/console/assets/channel/stable/v2.12/vendor.js.gz:1:2122624
e@https://graphql-engine-cdn.hasura.io/console/assets/channel/stable/v2.12/vendor.js.gz:1:2122723
rc@https://graphql-engine-cdn.hasura.io/console/assets/channel/stable/v2.12/vendor.js.gz:1:25862835
tc@https://graphql-engine-cdn.hasura.io/console/assets/channel/stable/v2.12/vendor.js.gz:1:25862628
Xl@https://graphql-engine-cdn.hasura.io/console/assets/channel/stable/v2.12/vendor.js.gz:1:25898482
Hl@https://graphql-engine-cdn.hasura.io/console/assets/channel/stable/v2.12/vendor.js.gz:1:25890133
Pl@https://graphql-engine-cdn.hasura.io/console/assets/channel/stable/v2.12/vendor.js.gz:1:25890056
Cl@https://graphql-engine-cdn.hasura.io/console/assets/channel/stable/v2.12/vendor.js.gz:1:25886906
ui/<@https://graphql-engine-cdn.hasura.io/console/assets/channel/stable/v2.12/vendor.js.gz:1:25837878
t.unstable_runWithPriority@https://graphql-engine-cdn.hasura.io/console/assets/channel/stable/v2.12/vendor.js.gz:1:25913689
oi@https://graphql-engine-cdn.hasura.io/console/assets/channel/stable/v2.12/vendor.js.gz:1:25837587
ui@https://graphql-engine-cdn.hasura.io/console/assets/channel/stable/v2.12/vendor.js.gz:1:25837825
si@https://graphql-engine-cdn.hasura.io/console/assets/channel/stable/v2.12/vendor.js.gz:1:25837758
El@https://graphql-engine-cdn.hasura.io/console/assets/channel/stable/v2.12/vendor.js.gz:1:25883658
enqueueSetState@https://graphql-engine-cdn.hasura.io/console/assets/channel/stable/v2.12/vendor.js.gz:1:25841611
_.prototype.setState@https://graphql-engine-cdn.hasura.io/console/assets/channel/stable/v2.12/vendor.js.gz:1:25786527
e@https://graphql-engine-cdn.hasura.io/console/assets/channel/stable/v2.12/vendor.js.gz:1:2112018
e/<@https://graphql-engine-cdn.hasura.io/console/assets/channel/stable/v2.12/vendor.js.gz:1:2112378

Any possible solutions?

Don't know.

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?

Don't know the source code well enough.

davidpanic commented 1 year ago

Also observed some weird requests in the developer console: image It's trying to reach out to https://data.undefined/v1/graphql

PopBot commented 1 year ago

Has there been an update? Still experiencing the same issue as of 6/19/2023. Thanks.

soorajshankar commented 1 year ago

Thanks for reporting this issue!

But unfortunately I couldn't reproduce this issue, following is how I tested. (There seem to be a different issue with button click only getting recognised on left side of the button- but this could be specific to my view port)

https://github.com/hasura/graphql-engine/assets/8408875/71f32ebd-0c16-45f1-b907-dd88f6afb5e9

Has there been an update? Still experiencing the same issue as of 6/19/2023. Thanks.

@PopBot, could you share some steps to reproduce along with a screencast if possible?

PopBot commented 1 year ago

@soorajshankar I'm so sorry that I forgot to post an update. We're running a self-hosted version of Hasura on Azure (latest version on Docker). It turns out we had accidentally added the aud claim to the Docker Config. After removing it, the Cognito JWK was picked up perfectly fine and Basic Auth worked.

Just a side note, the documentation for the AWS Lambdas functions for Cognito integration need to be updated for the latest Python and Node runtimes. Had spent a little too long working on that part.