graphprotocol / graphprotocol/graph-node
What are best practices for protecting deployment endpoints?
Open
@alex-pakalniskis is already working on this.
Since Apr 9, 2024.
community
Stale
- Dominant language
- Rust
- Stars
- 3.2k
- Forks
- 1.1k
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 1
Description
Trying to figure out how to protect a graph node and authenticate deployment requests. I see references to "graph auth" or --access-token parameters here and there, but cannot find any proper docs on any of this.
Does graph-node have any OOTB mechanism for this, or is this something that should be handled at another layer, for ex an Nginx reverse proxy that authenticates the requests?
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.
Assessment
This issue has not been assessed yet.