Permissions

Clase 24 de 54 • Full Stack JavaScript with Sails.js

Dallas

student•

IS there any robust tutorials on doing user login via actions2 , passport and storing successful login in a session store ie sails redis

Kelvin Omereshone

student•

Seems like something I can write on, In the Sailscasts blog. Look out for it here https://blog.sailscasts.com

Jason Stanley

student•

Two things.

Why wouldn't we just do the following to delete the item?

await Thing.destroy({id: inputs.id, owner: this.req.me.id});

Users shouldn't have an option to delete another users item in the UI. The approach in the code snippet has the following advantages.

If the user manages to issue two delete requests on an item they own this endpoint won't error now.
This approach removes a database query on this action.
This approach won't expose the ids of data created by other users.

Are we just doing it the way in the video to showcase the custom exit?

Is there a way to throw a forbidden response without specifying the exit?

A forbidden response is going to be fairly common and doesn't seem like the kind of thing which should be specified on every action which requires it. Perhaps I will get to it going forward. It would be good to know if common exits can be stored in a central place and called anywhere.

Adrien Riou

student•

Hi guys, I don't succeed to get the 403 error, I only have a 400 error "An expected error occured".

`module.exports = {

friendlyName: 'Destroy one thing',

description: 'Delete the "thing" with the specified ID from the database.',

inputs: { id: { type: 'number', required: true } },

exits: { forbidden: { description: 'The user making this request doesn't have the permissions to delete this thing.', respondeType: 'forbidden' } },

fn: async function (inputs, exists) {

var thing = await Thing.findOne({
  id: inputs.id
});

if(thing.owner !== this.req.me.id) {
  throw 'forbidden';
}

await Thing.destroy({ id: inputs.id });
// All done.
return;

} }; ` Someone could help me? Thanks a lot!

Dhruv Mishra

student•

for a weird reason my await doesn't work on the frontend

Mike USA

student•

@dhruv-mishra could you give more details by displaying the filename and the code

Permissions

Welcome to the course

Introduction and generalities

The technologies we are going to use

What we will build

Avoiding mistakes in our code

Github for our project

Installing platforms and dependencies

The essentials

Backend architecture

Frontend Architecture

ParasailsJS

Authentication and login

User Subscription

Sessions and Data Base

Password recovery

Email verification

Contact form

Managing payment information

Creating a new page

Making our page interactive

Creating a new model

Automatic testing

Creating a new action

Using Cloud SDK

Creating custom made functions

Personalization

Permissions

Friends with associations

Advanced queries and .populate

Modals

Ajax forms

Loading and error states

Putting it all together

Uploading backend file

Uploading frontend files

Downloading files

Your turn

Growth and monetization

Building a paywall

Recurrent payment subscriptions

Notifications

Invitations (Existing Users)

Invitations (New Users)

Unclaimed Accounts

Going live

SailsJS and NodeJS Settings

Application secutiry

Cloudflare and SSL Certifications

Using a platform as a service

Deploy to Heroku

Settings to send to production

Adding variables to Heroku

Data Base Settings

Before launching

Course Closure

Bonus content

Server-side rendering with EJS

Designing your frontend with Bootstrap 4

Understanding datastores

'Pure' APIs