data login logs you in with a simple experience using your existing social login.
Acceptance criteria
data login results in a token in your config file that you can use for further interaction with the API system
data login uses an existing social provider (e.g. Google) in browser to do login with a very easy experience
Tasks
Analysis
- (with conductor): check authorised, e.g. https://conductor/check?next=http://localhost:5432
- (conductor sends back): nope, here’s the google login url:
- Locally, start an http server listening on port 3000
- Locally, open a browser with that google login URL
- User authenticates with provider (i.e. Google/Github/...)
- If successfull authentication
- gets redirected to http://localhost:3000?jwt=
- Client stores the token and can return instructions to close window (or even just a <script>window.close();</script> response to close the browser window)
- (optional) Client now uses the token to retrieve user profile (name, email etc.)
- Client can now inform the user login was successful and go on with what it wanted to do.
- If unsuccessful
- gets redirected to http://localhost:3000 (no token)
- Client returns a <script>window.close();</script> response to close the browser window
- Client informs the user login had failed
data loginlogs you in with a simple experience using your existing social login.Acceptance criteria
data loginresults in a token in your config file that you can use for further interaction with the API systemdata loginuses an existing social provider (e.g. Google) in browser to do login with a very easy experienceTasks
(More) Tests for thisAnalysis