starred/hoppscotch

Fork 0

mirror of https://github.com/hoppscotch/hoppscotch.git synced 2026-04-26 01:06:00 +03:00

[GH-ISSUE #4276] [bug]: Introspection in GraphQL not working when OAuth2 is active #1553

New issue

Open

opened 2026-03-16 20:49:14 +03:00 by kerem · 4 comments

kerem commented

2026-03-16 20:49:14 +03:00

Owner

Originally created by @haarhoff-frs on GitHub (Aug 19, 2024).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4276

Is there an existing issue for this?

I have searched the existing issues

Current behavior

I have a GraphQL endpoint that requires OAuth2 authentification. When I click on "connect" in the GraphQL screen after entering the endpoind and filling out the authorization details, nothing happens and an error gets logged:

Error: Invalid or incomplete introspection result. Ensure that you are passing "data" property of introspection response and no "errors" was returned alongside: undefined.

The actual query I want to send does work.
When I allow anonymous access to the GraphQL endpoint, introspection works properly.

Steps to reproduce

Go to the GraphQL view
Enter a GraphQL endpoint that required OAuth2 authorization with client credentials
Enter credentials in the tab "Authorization"
Click on "Connect"
The connect button briefly flashes, the error message mentioned above is displayed in the console
Enter a query and click on "Run"
The query is executed normally
Enable anonymous access on the GraphQL server
Click on connect again
Introspection works

Environment

Production

Version

Cloud

Originally created by @haarhoff-frs on GitHub (Aug 19, 2024). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4276 ### Is there an existing issue for this? - [X] I have searched the existing issues ### Current behavior I have a GraphQL endpoint that requires OAuth2 authentification. When I click on "connect" in the GraphQL screen after entering the endpoind and filling out the authorization details, nothing happens and an error gets logged: ``` Error: Invalid or incomplete introspection result. Ensure that you are passing "data" property of introspection response and no "errors" was returned alongside: undefined. ``` The actual query I want to send does work. When I allow anonymous access to the GraphQL endpoint, introspection works properly. ### Steps to reproduce 1. Go to the GraphQL view 2. Enter a GraphQL endpoint that required OAuth2 authorization with client credentials 3. Enter credentials in the tab "Authorization" 4. Click on "Connect" 5. The connect button briefly flashes, the error message mentioned above is displayed in the console 6. Enter a query and click on "Run" 7. The query is executed normally 8. Enable anonymous access on the GraphQL server 9. Click on connect again 10. Introspection works ### Environment Production ### Version Cloud

kerem added the

bug

need testing

labels

2026-03-16 20:49:14 +03:00

kerem commented

2026-03-16 20:49:25 +03:00

Author

Owner

@ryanrixxh commented on GitHub (Sep 18, 2024):

I also receive this same error when using Bearer Token Authentication. Requests work, but schema introspection fails.

@ryanrixxh commented on GitHub (Sep 18, 2024): I also receive this same error when using Bearer Token Authentication. Requests work, but schema introspection fails.

kerem commented

2026-03-16 20:49:30 +03:00

Author

Owner

@ivank commented on GitHub (Nov 13, 2024):

Same error here - I think the "Connect" doesn't take Authorization headers into account at all.

@ivank commented on GitHub (Nov 13, 2024): Same error here - I think the "Connect" doesn't take Authorization headers into account at all.

kerem commented

2026-03-16 20:49:35 +03:00

Author

Owner

@johan-lindqvist commented on GitHub (Feb 19, 2025):

Any updates on this? Makes it very problematic to use in our case if introspection doesn't support any kind of authorization/api key

@johan-lindqvist commented on GitHub (Feb 19, 2025): Any updates on this? Makes it very problematic to use in our case if introspection doesn't support any kind of authorization/api key

kerem commented

2026-03-16 20:49:40 +03:00

Author

Owner

@FeuGuillaume186 commented on GitHub (Sep 1, 2025):

I have the same problem and it still hasn’t been resolved, it’s such a shame.

@FeuGuillaume186 commented on GitHub (Sep 1, 2025): I have the same problem and it still hasn’t been resolved, it’s such a shame.

kerem referenced this issue

2026-03-17 01:00:42 +03:00

[PR #1553] [MERGED] Suppletments some tranlations on zh-CN #3391

kerem referenced this issue

2026-03-17 01:01:31 +03:00

[PR #1572] [MERGED] i18n translations #3407