Support custom headers
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 102
- Forks
- 49
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 16
Description
When openfga is embedded in another application as library, there might be different authentication method in front of GRPC connection. For example, in grafana we use token-based authentication for GRPC connection to the service which embeds openfga. So in order to use openfga-cli we need to pass access token in special header which is not possible currently with CLI.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named. Start by locating the openfga-cli gRPC connection setup and its command-line option handling; trace how connection settings reach the service. Done means a caller can provide a custom access-token header and the CLI sends it when connecting to the embedded OpenFGA service.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication, cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100