Authentication

Introduction
Quick Start
Multi Authentication

Introduction

Hunt framework makes implementing authentication very simple. In fact, almost everything is configured for you out of the box.

At its core, Hunt framework's authentication facilities are based on Shiro and JWT. See https://github.com/dicoth/dicoth for more examples.

Quick Start

Prepare For The User's Data

There are two ways to provider all the user's data. One is through config files, the other is to implement the UserService interface.

Config file

By default, the Hunt framework will try to load the users‘s basic information from config/users:

# name, password, roles
admin  admin  superuser
Bob    test   user|manager

and load their roles and permissions from config/roles:

# name, permissions
superuser    user.add|user.del
manager      user.add|user.logout
user         user.profile|user.logout

Implementing the `UserService` interface

While implementing the UserService interface, you can load the user's data from anywhere:

class UserProviderService : UserService {
	// Implements all the APIs defined in UserService
}

Then register the user-defined UserService to the ServiceContainer as a ServiceProvider in the main entrace of your project like app.d or boostrap.d:

app.register!UserProviderService;

If a user-defined UserService is registered as ServiceProvider, the user's data will be loaded only from this ServiceProvider which means that the config files for user's data will be ignored automatically.

Guard or Authentication Scheme

There are two schemes you can choice in Hunt Framework. They are basic and jwt. You can set this in config/application.conf:

# guardScheme: (none), basic, bear/jwt
auth.guardScheme = jwt

base scheme

When you access a protected route via a browser like FireFox or Chrome, you will be prompted to input your username and password. Or, you can set them in the headers of the request like this:

Authorization: Basic YWRtaW46YWRtaW4=

After login, a cookie named __basic_token__ will be returnd if you set the rememeber to true when calling the signIn.

jwt scheme

First, you need to post your username and password to the login. Then, a cookie named __jwt_token__ will be returnd if you set the rememeber to true when calling the signIn.

Routes protection

To protect a route or a group of routes, you can call the withMiddleware method in the main entrace like app.d.

import app.providers;
import app.middleware;
import hunt.framework;

void main(string[] args)
    Application app = Application.instance();
    app.onBooted(() {
        // The default group
        app.route().get("index.security").withMiddleware!(AuthMiddleware)();

        // The admin group
        app.route().group("admin").withMiddleware(AuthMiddleware.stringof);
        app.route().group("admin").get("index.test").withoutMiddleware(AuthMiddleware.stringof);
    });
}

The withoutMiddleware method can be used to ignore some middlewares on one specified route. There is another way to do this. That's annotation Middleware and WithoutMiddleware, see belown:

class IndexController : Controller {
    @Middleware(AuthMiddleware.stringof)
    @Action string secret() {
        return "It's a secret page.";
    }

    @WithoutMiddleware(AuthMiddleware.stringof)
    @Action Response login(LoginUser user) {
        // do something
    }
}

Authenticating

The signIn method in request().auth() can be used to authorize a user. It will return a Identity, which identifies a user. You can use it to check the status of authentication and the role-based permissions.

class IndexController : Controller {
    @Middleware(AuthMiddleware.stringof)
    @Action string secret() {
        return "It's a secret page.";
    }

    @WithoutMiddleware(AuthMiddleware.stringof)
    @Action Response login(LoginUserForm user) {
        string username = user.name;
        string password = user.password;
        bool rememeber = user.rememeber;

        Identity authUser = this.request.auth().signIn(username, password, rememeber);
        string msg;
        if(authUser.isAuthenticated()) {
            msg = "User [" ~ authUser.name ~ "] logged in successfully.";
        } else {
            msg = "Login failed!";
        }
        return new Response(msg);
    }
}

Retrieving The Authenticated User

You may access the authenticated user via the auth method in Request.

	Identity currentUser = this.request.auth().user();

Retrieving The User's Name and ID

To retrieve the user's name and id, you may use the name and id method in Identity:

	string name = currentUser.name();
    ulong id = currentUser.id();

Determining If The Current User Is Authenticated

To determine if the user is already logged into your application, you may use the isAuthenticated method in Identity, which will return true if the user is authenticated:

    if (currentUser.isAuthenticated()) {
        // The user is logged in...
    }

Determining If The User Has The Roles

To determine if the user has some roles, you may use the hasRole or hasAllRoles method in Identity, which will return true if the user has the provided role(s):

    if (currentUser.hasRole("admin")) {
        // The user is an Administrator...
    }

    if (authUser.hasAllRoles("admin", "manager")) {
        // The user has all the roles
    }

Determining If The User's Permissions Is Permitted

To determine if the user is permitted, you may use the isPermitted method in Identity, which will return true if the user's has permissions passed:

    if (currentUser.isPermitted(["user.add", "user.del"])) {
        // The user is isPermitted
    }

Redirecting Unauthenticated Users

When the auth middleware detects an unauthorized user, it will redirect the user to the route specified by the unauthorizedUrl, which can be set in application.conf:

# Auth
auth.loginUrl = /login
auth.successUrl = /
auth.unauthorizedUrl = /403.html
auth.basicRealm = Secure Area

Logging Out

To manually log users out of your application, you may use the signOut method in Auth. This will clear the authentication information in the user's session:

class IndexController : Controller {
    @Action string logout() {
        Identity currentUser = this.request.auth().user();
        if(currentUser.isAuthenticated()) {
            this.request().auth().signOut();
            return "The user has logged out.";
        } else {
            return "No user logged in.";
        }
    }
}

Multi Authentication

In many cases, you need different authentications for different endpoints like admin, web and api etc. How to do this? Here are the steps:

Define constants

module app.auth.Constants;

enum string WEB_GUARD_NAME = "web";
enum string WEB_JWT_TOKEN_NAME = "__web_jwt_token__";

enum string ADMIN_GUARD_NAME = "admin";
enum string ADMIN_JWT_TOKEN_NAME = "__admin_jwt_token__";

The XXX_JWT_TOKEN_NAME is the token's name returnd to the visitor which is used to store the token value after authenticate. The XXX_GUARD_NAME is the custom guard's name which is used to identified the guard by Hunt Framework.

Implementing the UserService

Implementing the interface UserService for admin and web as above. As an example, we call them AdminUserService and WebUserService. The will be passed to the custom guards.

It's strongly recomended to put all the UserService in a named data folder.

Custom guards

You need to defined your own guard implement by inheriting from JwtGuard or BasicGuard.

It's strongly recomended to put all the guards in a named auth folder.

For admin

module app.auth.AdminGuard;

import app.auth.Constants;
import app.data.AdminUserService;
import hunt.framework;

class AdminGuard : JwtGuard {
    this() {
        super(new AdminUserService(), ADMIN_GUARD_NAME);
        this.tokenCookieName = ADMIN_JWT_TOKEN_NAME;
    }
}

For web

module app.auth.WebGuard;

import app.auth.Constants;
import app.data.WebUserService;
import hunt.framework;

class WebGuard : JwtGuard {
    this() {
        super(new WebUserService(), WEB_GUARD_NAME);
        this.tokenCookieName = WEB_JWT_TOKEN_NAME;
    }
}

Define an AuthServiceProvider

This AuthServiceProvider is used to register all the cusome guards.

module app.providers.DemoAuthServiceProvider;

import app.auth;
import hunt.framework;
import poodinis;

class DemoAuthServiceProvider : AuthServiceProvider {
    
    override void boot() {
        AuthService authService = container().resolve!AuthService();
        authService.addGuard(new AdminGuard());
        authService.addGuard(new UserGuard());

        authService.boot();
    }
}

It is used to replace the default guards impelemnted in Hunt Framework. So, it should be registered in app.d like this:

    app.register!DemoAuthServiceProvider;

Extend the AuthMiddleware

The default auth middleware defined in Hunt Framework is not suitable for multi authentication. Especially, after the authentication failed, you would redirect to different login route for admin and web.

module app.middleware.AdminAuthMiddleware;

import hunt.framework;
import std.range;

class AdminAuthMiddleware : AuthMiddleware {
    shared static this() {
        MiddlewareInterface.register!(typeof(this));
    }

    override protected bool onAccessable(Request request) {
        return true;
    }

    override protected Response onRejected(Request request) {
        return new RedirectResponse(request, url("system.user.login", null, "admin"));
    }
}

It's strongly recomended to put all the AuthMiddleware in a named middleware folder.

Binding the guards with the routes

Because all the routes use the default guard by default, we need bind our guards to the specified route group.

  app.onBooted(() {
        RouteGroup adminGroup = app.route().group("admin");
        adminGroup.guardName = ADMIN_GUARD_NAME;
        adminGroup.withMiddleware(AdminAuthMiddleware.stringof);
        adminGroup.get("system.user.login").withoutMiddleware(AdminAuthMiddleware.stringof); 

        RouteGroup userGroup = app.route().group();
        userGroup.guardName = USER_GUARD_NAME;       
    });

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

authorization.md

authorization.md

Authentication

Introduction

Quick Start

Prepare For The User's Data

Config file

Implementing the `UserService` interface

Guard or Authentication Scheme

Routes protection

Authenticating

Retrieving The Authenticated User

Retrieving The User's Name and ID

Determining If The Current User Is Authenticated

Determining If The User Has The Roles

Determining If The User's Permissions Is Permitted

Redirecting Unauthenticated Users

Logging Out

Multi Authentication

Files

authorization.md

Latest commit

History

authorization.md

File metadata and controls

Authentication

Introduction

Quick Start

Prepare For The User's Data

Config file

Implementing the UserService interface

Guard or Authentication Scheme

Routes protection

Authenticating

Retrieving The Authenticated User

Retrieving The User's Name and ID

Determining If The Current User Is Authenticated

Determining If The User Has The Roles

Determining If The User's Permissions Is Permitted

Redirecting Unauthenticated Users

Logging Out

Multi Authentication

Implementing the `UserService` interface