-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Auth:inherit not fully supported via Bruno CLI #3688
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.
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
Comments
Hey @tstavinoha Thanks for reporting this issue. |
Do we have any update on this? Facing the same issue while testing. |
Hi @abdullahkhilji, We're looking into this. I understand that we need to support a few authentication types in inherit. Could you clarify which one you're blocked on? Is it specifically API key authentication? |
Hi @anusree-bruno, Thanks for the update. It is the AWS Sig V4 authentication I am blocked on. |
Thanks @abdullahkhilji We have added this to our backlog. I will keep you updated on the progress |
We're using OAuth2 token authentication (with no header prefix, in case it matters) and would love to have this support. |
We use OAuth 2.0 authentication with Client Credentials (Add cred to request body + Add token to Headers with default param), we use autorefresh, but for a test/assert launch, I don't think we'll exceed the token validity time limit. In bruno the OAuth works, on requests as well as on collections. On the other hand, in CLI, the same files don't work (in requests and in collections). The certificates are good, the ClientSecret passed in --var-env is well interpreted. |
I have checked the following:
Describe the bug
It seems that Bruno CLI does not fully support all authentication methods in inherit mode.
In scope of a previous issue support for bearer token was added, alongside basic auth, but the other 5 methods do not seem to be supported. This is evident in the source code modified as part of the aforementioned issue.
I can try to help with the PR, but I was not sure how to migrate the logic from bruno-app module, as it differs significantly, and I'm not sure if it is the relevant part at all. I can try re-implementing it, at least for some cases (i'm mostly interested in API KEY method), but I'd like to find out whether this is a good way to proceed.
.bru file to reproduce the bug
bruno.json
collection.bru
Proof.bru
Screenshots/Live demo link
beeceptor set up to return 401 unless there is an Authorization header with any value..
Running via gui - works
Running via CLI
The text was updated successfully, but these errors were encountered: