liquidvotingio / liquidvotingio/auth
Support direct requests from the browser
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
In requests straight from javascript in the frontend, the consumer app server would be bypassed. In this case the key will be visible in the javascript source.
So supporting direct javascript requests will be more involved. One reference implementation is [Stripe publishable keys](https://stripe.com/docs/stripe-js/v2#setting-publishable-key)
_Originally posted in https://github.com/oliverbarnes/liquid-voting-auth/issues/2#issuecomment-619404375_
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 files, tests, or entry points are named. Start by reviewing the auth service and the issue's Stripe publishable-keys reference, then determine the design needed for direct browser requests while accounting for a key visible in JavaScript. Done means the service supports this request path with an agreed key-handling approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir, javascript
- Domain
- api, authentication
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100