Authentication and Authorization

Our todo app is nearly functionally complete, but it still doesn't fulfill a very basic requirement - that users should log in before they can view, create or modify tasks.

Remult provides a flexible mechanism that enables placing code-based authorization rules at various levels of the application's API. To maintain high code cohesion, entity and field-level authorization code should be placed in entity classes.

Remult is completely unopinionated when it comes to user authentication. You are free to use any kind of authentication mechanism, and only required to provide Remult with an object which implements the Remult UserInfo interface.

In this tutorial, we'll use Express's cookie-session middleware to store an authenticated user's session within a cookie. The user property of the session will be set by the API server upon a successful simplistic sign-in (based on username without password).

This rule is implemented within the Task @Entity decorator, by modifying the value of the allowApiCrud property. This property can be set to a function that accepts a Remult argument and returns a boolean value. Let's use the Allow.authenticated function from Remult.

// src/shared/Task.ts

@Entity("tasks", {
    allowApiCrud: Allow.authenticated
})

Import Allow

This code requires adding an import of Allow from remult.

After the browser refreshes, the list of tasks disappeared and the user can no longer create new tasks.

Inspect the HTTP error returned by the API using cURL

curl -i http://localhost:3002/api/tasks

Authorized server-side code can still modify tasks

Although client CRUD requests to tasks API endpoints now require a signed-in user, the API endpoint created for our setAllCompleted server function remains available to unauthenticated requests. Since the allowApiCrud rule we implemented does not affect the server-side code's ability to use the Task entity class for performing database CRUD operations, the setAllCompleted function still works as before.

To fix this, let's implement the same rule using the @BackendMethod decorator of the setAllCompleted method of TasksController.

// src/shared/TasksController.ts

@BackendMethod({ allowed: Allow.authenticated })

This code requires adding an import of Allow from remult.

User Authentication

Let's add a sign-in area to the todo app, with an input for typing in a username and a sign-in button. The app will have two valid username values - "Jane" and "Steve". After a successful sign-in, the sign-in area will be replaced by a "Hi [username]" message.

Backend setup

Open a terminal and run the following command to install the required packages:

npm i cookie-session
npm i --save-dev @types/cookie-session

Modify the main server module index.ts to use the cookie-session Express middleware.
ts
```
// src/server/index.ts

//...

import session from "cookie-session"

const app = express()
app.use(
  session({
    secret: process.env["SESSION_SECRET"] || "my secret"
  })
)

//...
```
The cookie-session middleware stores session data, digitally signed using the value of the secret property, in an httpOnly cookie, sent by the browser to all subsequent API requests.

Create a file src/server/auth.ts for the auth express router and place the following code in it:

// src/server/auth.ts

import express, { Router } from 'express'
import type { UserInfo } from 'remult'

const validUsers: UserInfo[] = [
  { id: '1', name: 'Jane' },
  { id: '2', name: 'Steve' },
]

export const auth = Router()

auth.use(express.json())

auth.post('/api/signIn', (req, res) => {
  const user = validUsers.find((user) => user.name === req.body.username)
  if (user) {
    req.session!['user'] = user
    res.json(user)
  } else {
    res.status(404).json("Invalid user, try 'Steve' or 'Jane'")
  }
})

auth.post('/api/signOut', (req, res) => {
  req.session!['user'] = null
  res.json('signed out')
})

auth.get('/api/currentUser', (req, res) => res.json(req.session!['user']))

The (very) simplistic signIn endpoint accepts a request body with a username property, looks it up in a predefined dictionary of valid users and, if found, sets the user's information to the user property of the request's session.
The signOut endpoint clears the user value from the current session.
The currentUser endpoint extracts the value of the current user from the session and returns it in the API response.

// src/server/index.ts

//...

import { auth } from "./auth"

const app = express()
app.use(
  session({
    secret: process.env["SESSION_SECRET"] || "my secret"
  })
)
app.use(auth)

//...

Frontend setup

Create an Auth component using Angular's cli
sh
```
ng g c auth
```

Add the highlighted code lines to the AuthComponent class file:

// src/app/auth/auth.component.ts

import { Component, OnInit } from '@angular/core'
import { CommonModule } from '@angular/common'
import { UserInfo, remult } from 'remult'
import { HttpClient, HttpClientModule } from '@angular/common/http'
import { FormsModule } from '@angular/forms'
import { TodoComponent } from '../todo/todo.component'

@Component({
  selector: 'app-auth',
  standalone: true,
  imports: [CommonModule, FormsModule, TodoComponent, HttpClientModule],
  templateUrl: './auth.component.html',
  styleUrl: './auth.component.css',
})
export class AuthComponent implements OnInit {
  constructor(private http: HttpClient) {}

  signInUsername = ''
  remult = remult

  signIn() {
    this.http
      .post<UserInfo>('/api/signIn', {
        username: this.signInUsername,
      })
      .subscribe({
        next: (user) => {
          this.remult.user = user
          this.signInUsername = ''
        },
        error: (error) => alert(error.error),
      })
  }

  signOut() {
    this.http
      .post('/api/signOut', {})
      .subscribe(() => (this.remult.user = undefined))
  }

  ngOnInit() {
    this.http
      .get<UserInfo>('/api/currentUser')
      .subscribe((user) => (this.remult.user = user))
  }
}

Replace the contents of auth.component.html with the following html:

html

<!-- src/app/auth/auth.component.html -->

<ng-container *ngIf="!remult.authenticated()">
  <h1>todos</h1>
  <main>
    <form (submit)="signIn()">
      <input
        [(ngModel)]="signInUsername"
        placeholder="Username, try Steve or Jane"
        name="username"
      />
      <button>Sign in</button>
    </form>
  </main>
</ng-container>
<ng-container *ngIf="remult.authenticated()">
  <header>
    Hello {{ remult.user?.name }}
    <button (click)="signOut()">Sign Out</button>
  </header>
  <app-todo></app-todo>
</ng-container>

Replace the TodoComponent with the AuthComponent in the AppComponent

//src/app/app.component.ts

import { Component, NgZone } from '@angular/core';
import { CommonModule } from '@angular/common';
import { RouterOutlet } from '@angular/router';
import { AuthComponent } from './auth/auth.component';
import { remult } from 'remult';

@Component({
  selector: 'app-root',
  standalone: true,
  imports: [CommonModule, RouterOutlet, AuthComponent],
  templateUrl: './app.component.html',
  styleUrl: './app.component.css',
})

Change the app.component.html to use the AuthComponent instead of the TodoComponent
html
```


<app-auth></app-auth>
```

Connect Remult middleware

Once an authentication flow is established, integrating it with Remult in the backend is as simple as providing Remult with a getUser function that extracts a UserInfo object from a Request.

// src/server/api.ts

//...

export const api = remultExpress({
  //...
  getUser: req => req.session!["user"]
})

The todo app now supports signing in and out, with all access restricted to signed in users only.

Role-based Authorization

Usually, not all application users have the same privileges. Let's define an admin role for our todo app, and enforce the following authorization rules:

All signed in users can see the list of tasks.
All signed in users can set specific tasks as completed.
Only users belonging to the admin role can create, delete or edit the titles of tasks.

Modify the highlighted lines in the Task entity class to reflect the top three authorization rules.

// src/shared/Task.ts

import { Allow, Entity, Fields, Validators } from "remult"

@Entity<Task>("tasks", {
  allowApiCrud: Allow.authenticated,
  allowApiInsert: "admin",
  allowApiDelete: "admin"
})
export class Task {
  @Fields.uuid()
  id!: string

  @Fields.string({
    validate: (task) => {
      if (task.title.length < 3) throw "Too Short"
    }
    allowApiUpdate: "admin"
  })
  title = ""

  @Fields.boolean()
  completed = false
}

Let's give the user "Jane" the admin role by modifying the roles array of her validUsers entry.

// src/server/auth.ts

const validUsers = [
  { id: "1", name: "Jane", roles: ["admin"] },
  { id: "2", name: "Steve" }
]

Sign in to the app as "Steve" to test that the actions restricted to admin users are not allowed. 🔒

Role-based Authorization on the Frontend

From a user experience perspective it only makes sense that users that can't add or delete, would not see these buttons.

Let's reuse the same definitions on the Frontend.

Modify the contents of todo.component.html to only display the form and delete buttons if these operations are allowed based on the entity's metadata:

html

<!-- src/app/todo/todo.component.html -->

<h1>todos</h1>
<main>
  <form *ngIf="taskRepo.metadata.apiInsertAllowed()" (submit)="addTask()">
    <input
      placeholder="What needs to be done?"
      [(ngModel)]="newTaskTitle"
      name="newTaskTitle"
    />
    <button>Add</button>
  </form>
  <div *ngFor="let task of tasks">
    <input
      type="checkbox"
      [(ngModel)]="task.completed"
      (change)="saveTask(task)"
    />
    <input [(ngModel)]="task.title" />
    <button (click)="saveTask(task)">Save</button>
    <button
      *ngIf="taskRepo.metadata.apiDeleteAllowed(task)"
      (click)="deleteTask(task)"
    >
      Delete
    </button>
  </div>
  <div>
    <button (click)="setAllCompleted(true)">Set all as completed</button>
    <button (click)="setAllCompleted(false)">Set all as uncompleted</button>
  </div>
</main>

This way we can keep the frontend consistent with the api's Authorization rules

Note We send the task to the apiDeleteAllowed method, because the apiDeleteAllowed option, can be sophisticated and can also be based on the specific item's values,

Authentication and Authorization ​

Tasks CRUD Requires Sign-in ​

User Authentication ​

Backend setup ​

Frontend setup ​

Connect Remult middleware ​

Role-based Authorization ​

Role-based Authorization on the Frontend ​