Initializer to allow to provide a proxy address so server-to-server integrations can occur
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 12.4k
- Forks
- 2.4k
- PR merge metrics
- No merged PRs in 30d
Description
## Motivation
Rather the access-token to be on the client side where it can be stolen and unexpected costs incurred. Your client library can point to my own server which i can verify the session with my users and me server to use the mapbox access-token, so all calls are then proxied to your servers. You could also provide a proxy library in different server side languages for ease of adoption.
## Design Alternatives
## Design
### Mock-Up
### Concepts
### Implementation
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
The issue names no files, tests, or initializer entry point. Start by locating the library initializer and the existing access-token request path, then clarify the proxy-address API and server-to-server scope with maintainers. Done should include an agreed design for routing calls through a user-controlled server and tests covering the configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100