Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: migrate loopback-example-passport repo as lb4 example #4899

Merged
merged 1 commit into from
Apr 20, 2020
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions examples/passport-login/.eslintignore
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
node_modules/
dist/
coverage/
8 changes: 8 additions & 0 deletions examples/passport-login/.eslintrc.js
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
// Copyright IBM Corp. 2020. All Rights Reserved.
// Node module: @loopback/example-passport-login
// This file is licensed under the MIT License.
// License text available at https://opensource.org/licenses/MIT

module.exports = {
extends: '@loopback/eslint-config',
};
64 changes: 64 additions & 0 deletions examples/passport-login/.gitignore
Original file line number Diff line number Diff line change
@@ -0,0 +1,64 @@
# Logs
logs
*.log
npm-debug.log*
yarn-debug.log*
yarn-error.log*

# Runtime data
pids
*.pid
*.seed
*.pid.lock

# Directory for instrumented libs generated by jscoverage/JSCover
lib-cov

# Coverage directory used by tools like istanbul
coverage

# nyc test coverage
.nyc_output

# Grunt intermediate storage (http://gruntjs.com/creating-plugins#storing-task-files)
.grunt

# Bower dependency directory (https://bower.io/)
bower_components

# node-waf configuration
.lock-wscript

# Compiled binary addons (http://nodejs.org/api/addons.html)
build/Release

# Dependency directories
node_modules/
jspm_packages/

# Typescript v1 declaration files
typings/

# Optional npm cache directory
.npm

# Optional eslint cache
.eslintcache

# Optional REPL history
.node_repl_history

# Output of 'npm pack'
*.tgz

# Yarn Integrity file
.yarn-integrity

# dotenv environment variables file
.env

# Transpiled JavaScript files from Typescript
/dist

# Cache used by TypeScript's incremental build
*.tsbuildinfo
2 changes: 2 additions & 0 deletions examples/passport-login/.npmignore
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
# Exclude *.tsbuildinfo - cache for tsc incremental builds
*.tsbuildinfo
1 change: 1 addition & 0 deletions examples/passport-login/.npmrc
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
package-lock=true
2 changes: 2 additions & 0 deletions examples/passport-login/.prettierignore
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
dist
*.json
6 changes: 6 additions & 0 deletions examples/passport-login/.prettierrc
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
{
"bracketSpacing": false,
"singleQuote": true,
"printWidth": 80,
"trailingComma": "all"
}
27 changes: 27 additions & 0 deletions examples/passport-login/LICENSE
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
Copyright (c) IBM Corp. 2020.
Node module: @loopback/example-passport-login
This project is licensed under the MIT License, full text below.

--------

MIT License

MIT License Copyright (c) IBM Corp. 2020

Permission is hereby granted, free of charge, to any person obtaining a copy of
this software and associated documentation files (the "Software"), to deal in
the Software without restriction, including without limitation the rights to
use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
the Software, and to permit persons to whom the Software is furnished to do so,
subject to the following conditions:

The above copyright notice and this permission notice (including the next
paragraph) shall be included in all copies or substantial portions of the
Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
202 changes: 202 additions & 0 deletions examples/passport-login/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,202 @@
# @loopback/example-passport-login

A tutorial for implementing authentication in LoopBack 4 using
[passport](https://github.com/jaredhanson/passport) modules.

- [Overview](#overview)
- [Prerequisites](#prerequisites)
- [Install](#install-the-example-locally)
- [Tutorial - Facebook](#Try-it-out-with-FaceBook)

## Overview

This example demonstrates how to use the LoopBack 4 features (like
`@authenticate` decorator, strategy providers, etc) with
[passport strategies](http://passportjs.org). It includes the local strategy as
well as oauth2 strategies to interact with external OAuth providers like
facebook, google,etc.

- Log in or Sign up into a LoopBack App using passport strategy modules
- Log in via external apps like Facebook or link those external profiles with a
LoopBack user (for example, a LoopBack user can have associated
facebook/google accounts to retrieve pictures).

## Prerequisites

Before starting this tutorial, make sure you have Client-ids/Secrets from third
party apps

- [facebook](https://developers.facebook.com/apps)
- [google](https://console.developers.google.com/project)
- [twitter](https://apps.twitter.com/) **Not yet implemented**

## Install the example locally

1. Run the `lb4 example` command to install `example-passport-login` repository:

```sh
lb4 example passport-login
```

2. change into directory and then install the required dependencies:

```sh
cd loopback4-example-passport-login && npm i
```

## Run the application

By default the user data is stored using a memory connector and saved locally to
`data/db.json`

Start the application with

```
$ npm start
```

## Test the login scenarios

Open browser to http://localhost:3000

### Scenario 1 : Sign up as a local user

1. Click on `Sign Up` from the header menu and register as a local user.
2. If the email provided during registration, matches with your account in
facebook or google you can link those profiles with your local account.
3. Click on `Login` from the header menu and enter registered email id and
password. The `View account` page loads with user information.

### Scenario 2 : Link external profiles with a local user

1. Click on `Login` from the header menu, You will see various buttons under
`Other login options`.
- [Facebook](#Try-it-out-with-FaceBook)
- [google](#Try-it-out-with-Google)
- `Twitter` - not yet implemented
2. When you click on any login option, the page is redirected to that social
app's login page. On successful login with the social app, the `View account`
page is loaded.
3. If the email-id registered in the social media app maches with a email-id
registered locally, then the profiles will be linked and the `View account`
page will display all the `linked accounts` for that locally registered user.
4. Click on Logout to log out of user session

### Scenario 3 : Sign up via an external Social Media app

1. Click on `Login` from the header menu, You will see various buttons under
`Other login options`.
- [Facebook](#Try-it-out-with-FaceBook)
- [google](#Try-it-out-with-Google)
- `Twitter` - not yet implemented
2. When you click on any login option, the page is redirected to that social
app's login page. On successful login with the social app, the `View account`
page is loaded.
3. If the email-id registered in the social media app does not match any
email-ids registered locally, then a new user is signed up. `View account`
page will display the external profile used to login under the
`linked accounts` section.
4. Click on Logout to log out of user session

## Try it out with FaceBook

### Create a test app and test user in FaceBook

1. Login to facebook developer console: https://developers.facebook.com/apps
2. Click on `My Apps` tab in the dashboard menu, and then select `Add a new App`
3. This loads the `App creation` page. Pick the platform as `Website` and then
enter app category, app name and "Site URL" (Skip the quick start)
4. Click `Settings` tab from the left hand side navigation menu, note the "App
ID" and "App Secret" and save
5. Click the `Roles` tab from the left hand side navigation menu, then the
`Test users` link under it, to display a list of test users. You can also
create a new test user.
6. On any listed test user, click the edit button to open an actions menu ->
click `Change permissions granted by this test user` and add [`email`,
`manage_pages`] scopes to permissions

- NOTE:
- Your app may not work if the settings are missing a contact email and/or
"Site URL".
- if you are testing locally, you can simply use `localhost:[port#]` as your
"Site URL".

### Create oauth2-providers.json

- Copy `oauth2-providers.template.json` from this example project's root to
`oauth2-providers.json`
- Update facebook oauth2 config with the values for `clientID/clientSecret` from
your test app.

```
"facebook-login": {
"provider": "facebook",
"module": "passport-facebook",
"clientID": "xxxxxxxxxxxxxxx",
"clientSecret": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
"callbackURL": "/auth/facebook/callback",
"authPath": "/auth/facebook",
"callbackPath": "/auth/facebook/callback",
"successRedirect": "/auth/account",
"failureRedirect": "/login",
"scope": ["email"],
"failureFlash": true,
"profileFields": ["gender", "link", "locale", "name", "timezone", "verified", "email", "updated_time"]
}
```

The `profileFields` field above tells facebook details to return in profile data
after authentication. For more information regarding the providers template, see
http://loopback.io/doc/en/lb2/Configuring-providers.json.html.

### Log in with Facebook

- Open your browser to the example app with, `http://localhost:3000`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@deepakrkris , thanks for making the UI changes and addressing my earlier comments.

Let's update this section with the latest UI changes in mind (some of the instructions are out of date.)

But also it is important to register a local user BEFORE any social media login, otherwise there will be issues.

  1. Open browser to localhost:3000
  2. Sign up as a local user with the email of a facebook test user you created above, and provide a password for local purposes. This registers a local user, and it will eventually be linked to social media credentials in the following steps.
  3. Login as this local user. You will be brought to the "View Account" tab ( and describe what they should see)
  4. Click on Sign Up or Login, and the pages indicate you've already logged in.
  5. Click on [Current User] button, and it calls https://localhost:3000/api/whoAmI endpoint and displays currently authenticated user.
  6. Click on Logout.
  7. Click on View Account, and you are not permitted since you are logged out.
  8. Look at the db.json and mention what they should see in there. User with specific email, and in UserCredentials, the password you enterered when you signed up.
  9. Now click on Login, and choose Login with Facebook. Enter the email of your facebook test user (same email you entered above), but specify the test user's facebook password (not local password).
  10. Upon successful FaceBook login, you are brought to View Account. (Explain the data they should see)
  11. Click on Sign Up or Login, and the pages indicate you are already logged in.
  12. Click on [Current User] to view the currently authenticated user.
  13. Click on Logout
  14. Click on View Account, and you are not allowed.
  15. Look at the db.json, there is still one user. It still has the UserCredentials entry as earlier, But now there is an entry in the UserIdentity section which contains the facebook profile info.
    At any time (authenticated or not), open http://localhost:3000/api/ping in the browser and you should see the ping info returned. This endpoint doesn't require authentication.

Please re-word my list above to your liking. But we need to hold the user's hand to explain our UI to have a sense of what the ui can do based on the endpoints we've secured. As well as the database info that helps tie the local and social stuff together.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also

image

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@emonddr agreed, this is fixed now

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@deepakrkris , thanks for making the UI changes and addressing my earlier comments.

Let's update this section with the latest UI changes in mind (some of the instructions are out of date.)

But also it is important to register a local user BEFORE any social media login, otherwise there will be issues.

  1. Open browser to localhost:3000
  2. Sign up as a local user with the email of a facebook test user you created above, and provide a password for local purposes. This registers a local user, and it will eventually be linked to social media credentials in the following steps.
  3. Login as this local user. You will be brought to the "View Account" tab ( and describe what they should see)
  4. Click on Sign Up or Login, and the pages indicate you've already logged in.
  5. Click on [Current User] button, and it calls https://localhost:3000/api/whoAmI endpoint and displays currently authenticated user.
  6. Click on Logout.
  7. Click on View Account, and you are not permitted since you are logged out.
  8. Look at the db.json and mention what they should see in there. User with specific email, and in UserCredentials, the password you enterered when you signed up.
  9. Now click on Login, and choose Login with Facebook. Enter the email of your facebook test user (same email you entered above), but specify the test user's facebook password (not local password).
  10. Upon successful FaceBook login, you are brought to View Account. (Explain the data they should see)
  11. Click on Sign Up or Login, and the pages indicate you are already logged in.
  12. Click on [Current User] to view the currently authenticated user.
  13. Click on Logout
  14. Click on View Account, and you are not allowed.
  15. Look at the db.json, there is still one user. It still has the UserCredentials entry as earlier, But now there is an entry in the UserIdentity section which contains the facebook profile info.
    At any time (authenticated or not), open http://localhost:3000/api/ping in the browser and you should see the ping info returned. This endpoint doesn't require authentication.

Please re-word my list above to your liking. But we need to hold the user's hand to explain our UI to have a sense of what the ui can do based on the endpoints we've secured. As well as the database info that helps tie the local and social stuff together.

@emonddr I have incorporated these steps as suitable for user readability. please review.

- Click on 'Log In' from the example app header menu
- Click on 'Log In with Facebook' button
- FaceBook login page opens, enter test user-id and password
- example app loads again on successful login
- redirect to example app will fail if facebook did not return profile with
email-id

## Try it out with Google

### Create test credentials in google

1. Login to google developer console: https://console.developers.google.com You
may have to create a sample project if you are new to google developer
console
2. Click on `OAuth consent screen` from the left hand side navigation menu,
select `External`, click `Create` button
3. This loads the `Application` page to register your app. Enter app name and
check if scopes has `email` permission
4. Click on `Credentials` link in the left hand side navigation menu
5. Then click `Create Credentials` tab, and select `OAuth Client ID`
6. This loads the `Create Client ID` page. Select application type as
`web application`, enter name and click `Create` button
7. A pop up loads with the created credentials. Note the displayed "Client ID"
and "Client Secret" and save

### Create oauth2-providers.json

- Copy `oauth2-providers.template.json` from this example project's root to
`oauth2-providers.json`
- Update google oauth2 config with the values for `clientID/clientSecret` from
your google test app.

```
"google-login": {
"provider": "google",
"module": "passport-google-oauth2",
"strategy": "OAuth2Strategy",
"clientID": "{google-client-id}",
"clientSecret": "{google-client-secret}",
"callbackURL": "/api/auth/thirdparty/google/callback",
"authPath": "/api/auth/thirdparty/google",
"callbackPath": "/api/auth/thirdparty/google/callback",
"successRedirect": "/auth/account",
"failureRedirect": "/login",
"scope": ["email", "profile"],
"failureFlash": true
}
```
12 changes: 12 additions & 0 deletions examples/passport-login/data/db.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
{
"ids": {
"User": 5,
"UserIdentity": 1007,
"UserCredentials": 3
},
"models": {
"User": {},
"UserIdentity": {},
"UserCredentials": {}
}
}
50 changes: 50 additions & 0 deletions examples/passport-login/data/oauth2-test-provider.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,50 @@
{
"facebook-login": {
"provider": "facebook",
"module": "passport-facebook",
"profileFields": ["gender", "link", "locale", "name", "timezone",
"verified", "email", "updated_time", "displayName", "id"],
"clientID": "1111",
"clientSecret": "app1_secret",
"callbackURL": "/api/auth/thirdparty/facebook/callback",
"authPath": "/api/auth/thirdparty/facebook",
"callbackPath": "/api/auth/thirdparty/facebook/callback",
"successRedirect": "/auth/account",
"failureRedirect": "/login",
"authorizationURL": "http://localhost:9000/oauth/dialog",
"tokenURL": "http://localhost:9000/oauth/token",
"profileURL": "http://localhost:9000/verify",
"scope": ["email"],
"failureFlash": true
},
"google-login": {
"provider": "google",
"module": "passport-google-oauth2",
"strategy": "OAuth2Strategy",
"clientID": "{google-client-id}",
"clientSecret": "{google-client-secret}",
"callbackURL": "/api/auth/thirdparty/google/callback",
"authPath": "/api/auth/thirdparty/google",
"callbackPath": "/api/auth/thirdparty/google/callback",
"successRedirect": "/auth/account",
"failureRedirect": "/login",
"scope": ["email", "profile"],
"failureFlash": true
},
"oauth2": {
"provider": "oauth2",
"module": "passport-oauth2",
"strategy": "OAuth2Strategy",
"authPath": "/api/auth/thirdparty/oauth2",
"callbackPath": "/api/auth/thirdparty/oauth2/callback",
"successRedirect": "/auth/account",
"failureRedirect": "/login",
"scope": ["email", "profile"],
"failureFlash": true,
"clientID": "1111",
"clientSecret": "app1_secret",
"callbackURL": "http://localhost:3000/api/auth/thirdparty/oauth2/callback",
"authorizationURL": "http://localhost:9000/oauth/dialog",
"tokenURL": "http://localhost:9000/oauth/token"
}
}
Loading