@loopback/example-shopping

This project aims to represent an online ecommerce platform APIs to validate / test the LoopBack 4 framework readiness for GA. See loopbackio/loopback-next#1476 for more information.

Installation

Make sure you have Node.js >= 8.9.0 installed. Then do the following to clone and start the project.

git clone https://github.com/strongloop/loopback4-example-shopping.git
cd loopback4-example-shopping
npm i
npm start

The main app will be running at http://[::1]:3000.

You will also see Recommendation server is running at http://127.0.0.1:3001., it is the server to which the services/recommender.service service will connect to get the recommendations for a user.

Usage

This app is intended to be interacted with using the API Explorer located at http://[::1]:3000/explorer/.

Models

This app has the following models:

1. User - representing the users of the system.
2. UserCredentials - representing sensitive credentials like a password.
3. Product - a model which is mapped to a remote service by services/recommender.service.
4. ShoppingCartItem - a model for representing purchases.
5. ShoppingCart - a model to represent a user's shopping cart, can contain many items (items) of the type ShoppingCartItem.
6. Order - a model to represent an order by user, can have many products (products) of the type ShoppingCartItem.

ShoppingCart and Order are marked as belonging to the User model by the use of the @belongsTo model decorator. Correspondingly, the User model is marked as having many Orders using the @hasMany model decorator. Although possible, a hasMany relation for User to ShoppingCart has not be created in this particular app to limit the scope of the example.

User is also marked as having one UserCredentials model using the @hasOne decorator. The belongsTo relation for UserCredentials to User has not been created to keep the scope smaller.

Controllers

Controllers expose API endpoints for interacting with the models and more.

In this app, there are four controllers:

1. ping - a simple controller to checking the status of the app.
2. user - controller for creating user, fetching user info, updating user info, and logging in.
3. shopping-cart - controller for creating, updating, deleting shopping carts, and getting the details about a shopping cart.
4. user-order - controller for creating, updating, deleting orders, and getting the details about an order.

Services

Services are modular components that can be plugged into a LoopBack application in various locations to contribute additional capabilities and features to the application.

This app has five services:

1. services/recommender.service - responsible for connecting to a "remote" server and getting recommendations for a user. The API endpoint at GET /users​/{userId}​/recommend, is made possible by this service.
2. services/user-service - responsible for verifying if user exists and the submitted password matches that of the existing user.
3. services/hash.password.bcryptjs - responsible for generating and comparing password hashes.
4. services/validator - responsible for validating email and password when a new user is created.
5. services/jwt-service - responsible for generating and verifying JSON Web Token.

Authentication

Note: This app contains a login endpoint for the purpose of spike and demo, the authentication for the CRUD operations and navigational endpoints of model User is still in progress.

Login

The endpoint for logging in a user is a POST request to /users/login.

Once the credentials are extracted, the logging-in implementation at the controller level is just a four step process. This level of simplicity is made possible by the use of the UserService service provided by @loopback/authentication.

1. const user = await this.userService.verifyCredentials(credentials) - verify the credentials.
2. const userProfile = this.userService.convertToUserProfile(user) - generate user profile object.
3. const token = await this.jwtService.generateToken(userProfile) - generate JWT based on the user profile object.
4. return {token} - send the JWT.

You can see the details in packages/shopping/src/controllers/user.controller.ts.

Authorization

To see authorization in action in this example, all requests to the endpoint /users/{userId}/orders (i.e, UserOrderController) are validated for specific user access.

Endpoint authorization is done using @loopback/authorization package and the provisions in it are implemented using Casbin configurations.

Below is a scenario illustrating how authorization works in this example:

1. Bob logs into the shopping app using his existing user credential via endpoint /users/login. The JWT token returned has the user name as bob and id as 123.

2. Bob invokes endpoint GET /users/123/orders with the JWT token obtained in the previous step. The corresponding controller operation findOrders is configured authorization scope ['find'].

3. The authorization provider in packages/shopping/src/services/authorizor.ts uses the casbin configuration /packages/shopping/fixtures/casbin/rbac_policy.csv to validate that bob has find scope for resource order.

4. Bob invokes endpoint DELETE /users/123/orders with the JWT token. The endpoint operation in the controller deleteOrders is configured with @authorize decorator with scopes ['delete']. The decorator also has a voter function (packages/shopping/src/services/id.compare.authorizor.ts) to check if the userId in the path matches with the user id in the JWT token. This serves as an additional data level restriction to avoid tokens of other users delete bob's orders.

Tutorial

There is a tutorial which shows how to apply the JWT strategy to secure your endpoint with @loopback/[email protected]. You can check more details in https://loopback.io/doc/en/lb4/Authentication-Tutorial.html

Trying It Out

Please check the try it out section in the tutorial.

Deploy to Cloud as Microservices

The example application can be packaged as multiple Docker containers and deployed to a cloud environment as a Kubernetes cluster.

Please check out Deploy Shopping Application as Cloud-native Microservices.

Contributing

This project uses DCO. Be sure to sign off your commits using the -s flag or adding Signed-off-By: Name<Email> in the commit message.

Example

git commit -s -m "feat: my commit message"

Other LoopBack 4 Guidelines apply. See the following resources to get you started:

• Contributing Guidelines
• Developing LoopBack

Team

See all contributors.

License

MIT