dyorg/slim-token-authentication

Slim 3.0+ Token Authentication Middleware

Slim Token Authentication

This is a Token Authentication Middleware for Slim 3.0+. This middleware was designed to maintain easy to implement token authentication with custom authenticator., _(*1)

Installing

Get the latest version with Composer., _(*2)

composer require dyorg/slim-token-authentication

Getting authentication

Start by creating an authenticator function, this function will make the token validation of your application. When you create a new instance of TokenAuthentication you must pass an array with configuration options. You need setting authenticator and path options for authentication to start working., _(*3)

$authenticator = function($request, TokenAuthentication $tokenAuth){

    # Search for token on header, parameter, cookie or attribute
    $token = $tokenAuth->findToken($request);

    # Your method to make token validation
    $user = User::auth_token($token);

    # If occured ok authentication continue to route
    # before end you can storage the user informations or whatever
    ...

};

$app = new App();

$app->add(new TokenAuthentication([
    'path' => '/api',
    'authenticator' => $authenticator
]));

Find Token

This middleware contains the method findToken(), you can access it from your authenticator method through the second param (TokenAuthentication instance). This method is able to search for authentication token on header, parameter, cookie or attribute. You can configure it through options settings., _(*4)

Configuration Options

Path

By default no route requires authentication. You must set one or more routes to be restricted by authentication, setting it on path option., _(*5)

...

$app = new App();

$app->add(new TokenAuthentication([
    'path' => '/api', /* or ['/api', '/docs'] */
    'authenticator' => $authenticator
]));

Passthrough

You can configure which routes do not require authentication, setting it on passthrough option., _(*6)

...

$app = new App();

$app->add(new TokenAuthentication([
    'path' => '/api',
    'passthrough' => '/api/auth', /* or ['/api/auth', '/api/test'] */
    'authenticator' => $authenticator
]));

Header

By default middleware tries to find token from Authorization header. You can change header name using header option. Is expected in Authorization header the value format as Bearer <token>, it is matched using a regular expression. If you want to work without token type or with other token type, like Basic <token>, you can change the regular expression pattern setting it on regex option. You can disabled authentication via header by setting header option as null., _(*7)

...

$app->add(new TokenAuthentication([
    'path' => '/api',
    'authenticator' => $authenticator,
    'header' => 'Token-Authorization-X',
    'regex' => '/Basic\s+(.*)$/i', /* for without token type can use /\s+(.*)$/i */
]));

Parameter

If token is not found in header, middleware tries to find authorization query parameter. You can change parameter name using parameter option. You can disable authentication via parameter by setting parameter option as null., _(*8)

...

$app->add(new TokenAuthentication([
    'path' => '/api',
    'authenticator' => $authenticator,
    'parameter' => 'token'
]));

Cookie

If token is not found yet, middleware tries to find authorization cookie. You can change cookie name using cookie option. You can disabled authentication via cookie by setting cookie option as null., _(*9)

...

$app->add(new TokenAuthentication([
    'path' => '/api',
    'authenticator' => $authenticator,
    'cookie' => 'token'
]));

Argument

As a last resort, middleware tries to find authorization argument of route. You can change argument name using argument option. You can disabled authentication via argument by setting argument option as null., _(*10)

...

$app->add(new TokenAuthentication([
    'path' => '/api',
    'authenticator' => $authenticator,
    'argument' => 'token'
]));

Error

By default on ocurred a fail on authentication, is sent a response on json format with a message (Invalid Token or Not found Token) and with the token (if found), with status 401 Unauthorized. You can customize it by setting a callable function on error option., _(*11)

...

$error = function($request, $response, TokenAuthentication $tokenAuth) {
    $output = [];
    $output['error'] = [
        'msg' => $tokenAuth->getResponseMessage(),
        'token' => $tokenAuth->getResponseToken(),
        'status' => 401,
        'error' => true
    ];
    return $response->withJson($output, 401);
}

$app = new App();

$app->add(new TokenAuthentication([
    'path' => '/api',
    'authenticator' => $authenticator
    'error' => $error
]));

This error function is called when TokenAuthentication catches a throwable class that implements UnauthorizedExceptionInterface., _(*12)

Secure

Tokens are essentially passwords. You should treat them as such and you should always use HTTPS. If the middleware detects insecure usage over HTTP it will return unathorized with a message Required HTTPS for token authentication. This rule is relaxed for requests on localhost. To allow insecure usage you must enable it manually by setting secure to false., _(*13)

...

$app = new App();

$app->add(new TokenAuthentication([
    'path' => '/api',
    'authenticator' => $authenticator,
    'secure' => false
]));

Alternatively you can list your development host to have relaxed security., _(*14)

...

$app->add(new TokenAuthentication([
    'path' => '/api',
    'authenticator' => $authenticator,
    'secure' => true,
    'relaxed' => ['localhost', 'your-app.dev']
]));

Example

See how use it on /example., _(*15)

License

The MIT License (MIT). Please see License for more information., _(*16)