How to pass the authorization token as header information

[sharathchandramg]

Hi,
I have my grpc service behind an API gateway. The gateway protects the service using an API key. I am able to use the above using grpcurl as follows:

grpcurl \
-H 'Authorization:<api_key>\
-d '{}' \
<endpoint>.cloudapp.azure.com:8080 \
<namespace>.HelloService/SayHello

I want to load test the same thing using ghz and I am facing issues in calling using the metadata

ghz \
-m '{"Authorization" : "<api_key>"}' \
--call <namespace>..HelloService/SayHello \
-d '{}' \
<endpoint>.cloudapp.azure.com:8080

I keep getting the error

rpc error: code = Unauthenticated desc = unexpected HTTP status code received from server: 401 (Unauthorized); transport: received unexpected content-type "application/json"

[KeganHollern]

Also having this issue

[is-jonreeves]

We are also running into the same issue. Requests work fine with grpcurl but not with ghz

Our Header format is Authorization: Bearer <token>.

[GoToCoding]

Try ghz --metadata="{\"authorization\": \"Bearer $TOKEN\"}"
It works fine for me.

[jwillker]

I have already tried many different ways to do that, and it still doesn't work with Ghz, but it perfectly works with grpcurl.

[softprops]

also seeing this what works grpcurl works with -H "Authorization: Bearer $TOKEN" but ghz does not with --metadata="{\"authorization\": \"Bearer $TOKEN\"}"

[softprops]

If it helps move things along here is what grpcurl does to tranform headers into metadata