New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[bug]: Auth headers not being passed to GraphQL calls when added to collection #207

Open

jnovak-SM2Dev opened this issue Apr 4, 2024 · 0 comments

jnovak-SM2Dev commented Apr 4, 2024

Describe the bug
Adding a bearer auth token to a collection does not seem to pass an authorization header to GraphQL calls.

To Reproduce
Steps to reproduce the behavior:

Go to collection
Select view details
Select Bearer as auth type
Add a token
Go to a nested GraphQL call
Run it, it does not pass an authorization header

Expected behavior
It should path the authorization header.

Desktop (please complete the following information):

OS: Mac OS
Version 3.3.0-beta.3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment