• Username / Password
• Login using google
• Login using facebook
• Login using github

example of unit testing can be found here
https://github.com/plumier/tutorial-todo-sql-backend/blob/master/test/todo-auth.spec.ts

• Facebook login
• Google login
• Github login

Example callback is here https://github.com/plumier/plumier/blob/master/packages/plumier/test/integration/social-login/controller/google-controller.ts

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet.
We recommend using:

• CircleCI
• Travis CI
• Buildkite
• CodeShip
• Azure Pipelines
• TeamCity
• Buddy
• AppVeyor
  But Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

connect the Login function with the UI

I know this is just a simple app for tutorial, but how the ui check if user is authenticated is a bit annoy me . It's not necessary to create a flag in sessionStorage indicated that user is authenticated, while you already use cookie as authentication method. Currently when i delete flag value in sessionStorage, user will marked as not authenticated and must relogin, meanwhile actually we still can access the rest api method because cookie still exist

My suggestion is, server need to create a rest api method to check user's authenticated status by checking it's cookie, and then UI can consume this method to define user status.