It is unclear if gRPC calls can be authenticated
- Dominant language
- JavaScript
- Stars
- 34
- Forks
- 70
- PR merge metrics
- No merged PRs in 30d
Description
### Code of Conduct
- [x] I have read and agree to the Insomnia Docs project's [Code of Conduct](https://github.com/Kong/insomnia-docs/blob/main/CODE_OF_CONDUCT.md).
### What article on docs.insomnia.rest is affected?
[This](https://docs.insomnia.rest/insomnia/grpc) page begs the question: why doesn't grpc requests have the`Auth` tab
like the REST one?
Is it because authentication isn't supported? Is it because it needs enabling somewhere? Can Insomnia really claim it supports gRPC if it doesn't support [OAuth2 authentication](https://grpc.io/docs/guides/auth/#using-oauth-token-based-authentication) for it?
### What part(s) of the article would you like to see updated?
https://docs.insomnia.rest/insomnia/grpc#known-limitations ? The term "authentication" has to be present on the https://docs.insomnia.rest/insomnia/grpc page in some form somewhere.
### Additional information
_No response_
### Code of Conduct and Community Expectations
- [x] I agree to follow this project's Code of Conduct
- [x] I agree to abide by the Community Expectations
Contributor guide
Research direction
Start with the gRPC article at docs.insomnia.rest/insomnia/grpc, especially its Known Limitations section, and verify whether Insomnia supports authentication for gRPC requests, including OAuth2. Update the article so the authentication behavior and any limitations are explicit; done means the page directly answers whether gRPC calls can be authenticated.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100