vectordotdev / vectordotdev/vector
Auth between Vectors
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 22.6k
- Forks
- 2.3k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 146
Description
Problem: We expose vector instances to our clients or untrusted environments. Currently, any client is able to push data using GRPC.
Current solution: create mutual TLS or private communication networks. This is good in terms of security but complicates the infrastructure and sometimes it's not possible / not required.
Suggestions:
- Create a secret token (shared secret) which can be injected via config and/or env variable. Can be done as a quick solution for "vector" source-sink and will solve our problem.
- Implement global authorization schema which can be exposed to various sources-sinks (vector, http, etc.).
- other options ?
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
Start with the gRPC source-sink path and current configuration or environment-variable handling; compare it with the existing mutual TLS and private-network approach. Clarify whether the first deliverable is a shared token for vector source-sink or a global authorization schema, then verify that clients without the required credentials cannot push data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc, rust
- Domain
- api, authentication, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100