How to use Goth With React Applications
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.6k
- Forks
- 631
- PR merge metrics
- No merged PRs in 30d
Description
Currently goth does all the authentication on a single port. I have a use case where the user will click
on a button on UI which is React Application saying `Sign In With Github` and other buttons with other
provider name running on a different port. UI will send request to goth server and goth server should retun
user details once authenticated
In short
React Application running on port 3000
Once clicked on button request should be send to goth server running on a port say 4200, does all authentication process and once authenticated goth server returns user details back to React Application
Contributor guide
No contributing guide indexed for this repository
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
This is a cross-origin authentication and integration question rather than a scoped code change; no files or tests are named. Start by tracing Goth's server-side authentication flow and the React application's request/callback boundary; done would be a documented, agreed integration path for the separate ports and provider buttons.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, react
- Domain
- authentication, backend, frontend
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100