hapi-auth-cookie
hapi Cookie authentication plugin
Lead Maintainer: James Weston
Cookie authentication provides simple cookie-based session management. The user has to be authenticated via other means, typically a web form, and upon successful authentication the browser receives a reply with a session cookie. The cookie uses Iron to encrypt and sign the session content.
Subsequent requests containing the session cookie are authenticated and validated via the provided validateFunc
in case the cookie's encrypted content requires validation on each request.
It is important to remember a couple of things:
- Each cookie operates as a bearer token and anyone in possession of the cookie content can use it to impersonate its true owner.
- Cookies have a practical maximum length. All of the data you store in a cookie is sent to the browser. If your cookie is too long, browsers may not set it. Read more here and here. If you need to store more data, store a small amount of identifying data in the cookie and use that as a key to a server-side cache system.
The 'cookie
' scheme takes the following required options:
cookie
- the cookie name. Defaults to'sid'
.password
- used for Iron cookie encoding. Should be at least 32 characters long.ttl
- sets the cookie expires time in milliseconds. Defaults to single browser session (ends when browser closes). Required whenkeepAlive
istrue
.domain
- sets the cookie Domain value. Defaults to none.path
- sets the cookie path value. Defaults to/
.clearInvalid
- iftrue
, any authentication cookie that fails validation will be marked as expired in the response and cleared. Defaults tofalse
.keepAlive
- iftrue
, automatically sets the session cookie after validation to extend the current session for a newttl
duration. Defaults tofalse
.isSameSite
- iffalse
omitted. Other optionsStrict
orLax
. Defaults toStrict
.isSecure
- iffalse
, the cookie is allowed to be transmitted over insecure connections which exposes it to attacks. Defaults totrue
.isHttpOnly
- iffalse
, the cookie will not include the 'HttpOnly' flag. Defaults totrue
.redirectTo
- optional login URI to redirect unauthenticated requests to. Note that usingredirectTo
with authentication mode'try'
will cause the protected endpoint to always redirect, voiding'try'
mode. To set an individual route to use or disable redirections, use the routeplugins
config ({ config: { plugins: { 'hapi-auth-cookie': { redirectTo: false } } } }
). Defaults to no redirection.appendNext
- iftrue
andredirectTo
istrue
, appends the current request path to the query component of theredirectTo
URI using the parameter name'next'
. Set to a string to use a different parameter name. Defaults tofalse
.redirectOnTry
- iffalse
and route authentication mode is'try'
, authentication errors will not trigger a redirection. Requires hapi version 6.2.0 or newer. Defaults totrue
;validateFunc
- an optional session validation function used to validate the content of the session cookie on each request. Used to verify that the internal session state is still valid (e.g. user account still exists). The function has the signaturefunction(request, session, callback)
where:request
- is the Hapi request object of the request which is being authenticated.session
- is the session object set viarequest.cookieAuth.set()
.callback
- a callback function with the signaturefunction(err, isValid, credentials)
where:err
- an internal error.isValid
-true
if the content of the session is valid, otherwisefalse
.credentials
- a credentials object passed back to the application inrequest.auth.credentials
. If value isnull
orundefined
, defaults tosession
. If set, will override the current cookie as ifrequest.cookieAuth.set()
was called.
requestDecoratorName
- USE WITH CAUTION an optional name to use with decorating therequest
object. Defaults to'cookieAuth'
. Using multiple decorator names for separate authentication strategies could allow a developer to call the methods for the wrong strategy. Potentially resulting in unintended authorized access.
When the cookie scheme is enabled on a route, the request.cookieAuth
objects is decorated with
the following methods:
set(session)
- sets the current session. Must be called after a successful login to begin the session.session
must be a non-null object, which is set on successful subsequent authentications inrequest.auth.credentials
where:session
- the session object.
set(key, value)
- sets a specific object key on the current session (which must already exist) where:key
- session key string.value
- value to assign key.
clear([key])
- clears the current session or session key where:key
- optional key string to remove a specific property of the session. If none provided, defaults to removing the entire session which is used to log the user out.
ttl(msecs)
- sets the ttl of the current active session where:msecs
- the new ttl in milliseconds.
Because this scheme decorates the request
object with session-specific methods, it cannot be
registered more than once.
'use strict'; const Hapi = ; let uuid = 1; // Use seq instead of proper unique identifiers for demo only const users = john: id: 'john' password: 'password' name: 'John Doe' ; const home = { ;}; const login = { if requestauthisAuthenticated return reply; let message = ''; let account = null; if requestmethod === 'post' if !requestpayloadusername || !requestpayloadpassword message = 'Missing username or password'; else account = usersrequestpayloadusername; if !account || accountpassword !== requestpayloadpassword message = 'Invalid username or password'; if requestmethod === 'get' || message return ; const sid = String++uuid; requestserverappcache;}; const logout = { requestcookieAuthclear; return reply;}; const server = ;server; server;