training.shoppinpal.com
  • Introduction
  • 1. The Ideal Workspace
    • The Perfect Machine
      • For Biz Team
      • For Developers
      • For Designers
    • Setup a machine in the cloud
      • Solution
      • Setup box on Azure
        • Create a machine on Azure
        • Test drive your remote machine
        • Setup Dropbox On Azure
      • Setup box on DigitalOcean
        • Setup UI
        • Shared FileSystem
          • Dropbox
            • Use locally developed node modules in another project
          • sshfs
        • Long Running Sessions
      • Feedback
  • 2. Learning Git
    • Static Code Analysis
  • 3. The Backend
    • Use Containers
    • Setup a loopback project
    • Lockdown
    • Build a better mousetrap
    • The abyss stares back
    • Built-in models
    • Extending built-in models
    • Understanding UserModel
    • Boot Scripts
    • Promises
    • Find roles for current user
    • Loopback Console
    • Current User
  • 4. Multi-tenancy With Loopback
    • What is Multi-Tenancy
    • Architecting with Loopback
    • Define scope for Roles
    • Role Resolvers
    • Access Control For Tenants
    • Better Programming with multi-tenancy
  • 5. The Frontend
    • The Browser
    • Unit Testing
      • Motivation behind this blog
      • How to write a test
      • Karma and Jasmin
      • Writing Tests
    • End-2-End Testing
    • Angular 1.x
    • Angular 2
      • Testing
  • 6. ElasticSearch
    • Better Search with NGram
    • NGram with Elasticsearch
    • Fun with Path Hierarchy Tokenizer
    • Working with Mappings and Analyzers
  • 7. Promises
    • What are Promises
    • Promise Implementations
    • Nuances
    • What should we use
  • 8. Learning Docker
    • Docker Swarm
  • 9. Queues & Workers
    • PHP workers in AWS EBS
    • NodeJS workers in AWS EBS
      • SQS Daemon by AWS
      • SQS Daemon in NodeJS
      • SQS polling by worker
    • Gearman
  • 10. Docker
    • Capabilities
  • Appendix
    • Bug in WebStorm deployments
    • The Perfect Terminal
    • Scalable App Deployment with AWS
    • Chrome Tips & Tricks
    • Host your own Gitbook
    • Gitbook Tips & Tricks
    • How to handle support incidents
    • Dev Resources
    • Debug e2e Tests on CircleCI
    • Logging
    • Authentication Principles
    • Mac
    • nvm
    • Unify testing with npm
      • Debugging Mocha
    • Sequence Diagrams
    • Project Sync via IDE
      • SFTP with WebStorm
      • SFTP with Visual Studio
    • Soft Linking
    • NodeJS Profiling
      • How to find node.js performance optimization killers
    • Setup Packer on Azure
Powered by GitBook
On this page
  1. 3. The Backend

Find roles for current user

a) Update the relations block of common/models/user-model.json file like so:

  "relations": {
      "roles": {
          "type": "hasMany",
          "model": "Role",
          "through": "RoleMapping",
          "foreignKey": "principalId"
      }
  },

b) But before we can test this, we need as accessToken to use in the UI explorer to make the call. How can we do that? We can resuse the one we retieved in the last section from the logs.

c) Start the server with: cd ~/workspace/loopback-zero-to-hero/ && DEBUG=server:boot:*,boot:02-load-users node .

$ cd ~/workspace/loopback-zero-to-hero/ && DEBUG=server:boot:*,boot:02-load-users node .
Browse your REST API at http://0.0.0.0:3000/explorer
Web server listening at: http://0.0.0.0:3000/
  server:boot:01-seed-data Its alive! +0ms
  boot:02-load-users Creating roles and users +1ms
  boot:02-load-users found role +209ms admin
  boot:02-load-users found role +0ms users
  boot:02-load-users found user +1ms admin
  boot:02-load-users found user +3ms user
  server:boot:03-login-users (1) created +3s AccessToken {
  "id": "ACKQJqLNktnr1Rovsb3hluoGtqMiakSBrxntcdFKy6nEl29dsUYFksM4NUNQ9DHo",
  "ttl": 1209600,
  "created": "2015-07-06T21:37:56.821Z",
  "userId": 1
}

d) Copy a token string from the logs

e) Launch the browser at: <public_url>:3000/explorer

f) Paste the token into the textbox on the top right of the explorer UI and click the Set Access Token button

g) Access the roles via an api call at: <public_url>:3000/explorer/#!/UserModels/findById

g.1) fill in the filter field with: {"include":"roles"}

g.2) as for the id field, you can pick out its value from the logs around the same place you found the access token, look for userId in the logs:

server:boot:03-login-users (1) created +3s AccessToken {
  "id": "ACKQJqLNktnr1Rovsb3hluoGtqMiakSBrxntcdFKy6nEl29dsUYFksM4NUNQ9DHo",
  "ttl": 1209600,
  "created": "2015-07-06T21:37:56.821Z",
  "userId": 1
}

g.3) Click the Try it out! button and you should see a response like:

{
  "username": "admin",
  "email": "admin@admin.com",
  "id": 1,
  "firstName": "Admin",
  "lastName": "User",
  "roles": [
    {
      "id": 1,
      "name": "admin",
      "created": "2015-07-05T03:06:07.989Z",
      "modified": "2015-07-05T03:06:07.989Z"
    }
  ]
}

which has the roles information included in it.

PreviousPromisesNextLoopback Console

Last updated 7 years ago