Opinionated user management service for AdonisJs

Make sure @adonisjs/framework version is >= 5.0.6

AdonisJs is all about removing redundant code from your code base. This add-on tries to do the same.

Persona is a simple, functional service to let you create, verify and update user profiles.

Persona is not for everyone; if your login system is too complex and relies on many factors, Persona is not for you. However, persona works great for most use cases.

1. Helps you register new users.
2. Generates email verification tokens.
3. Validates credentials on login.
4. On email change, sets the user account to a pending state and re-generates the email verification token.
5. Allows changing passwords.
6. Allows recovering forgotten passwords.

1. Does not generate any routes, controllers or views for you.
2. Does not send emails. However, it emits events that you can use to send emails.
3. Does not create sessions or generate JWT tokens.

Run the following command to grab the add-on from npm:

adonis install @adonisjs/persona

# for yarn
adonis install @adonisjs/persona --yarn

Follow up by registering the provider inside the providers array:

const providers = [
  '@adonisjs/persona/providers/PersonaProvider'
]

You may then access it as follows:

const Persona = use('Persona')

The config file is saved as config/persona.js.

There are some intentional constraints in place.

1. Only works with Lucid models.

2. The App/Models/User must have a relationship setup with App/Models/Token and vice-versa.

   class User extends Model {
     tokens () {
       return this.hasMany('App/Models/Token')
     }
   }
   
   class Token extends Model {
     user () {
       return this.belongsTo('App/Models/User')
     }
   }

3. User table must have a string column called account_status.

Let's go through the API of persona.

The optional callback is invoked with the original payload just before the user is saved to the database. You can use it if you need to attach any other properties to the payload.

The register method takes the user input data and performs the following actions on it.

1. Validates that all uids are unique.
2. Checks that email is unique and is a valid email address.
3. Makes sure the password is confirmed.
4. Creates a new user account with the account_status = pending.
5. Generates and saves an email verification token inside the tokens table.
6. Emits a user::created event. You can listen for this event to send an email to the user.

Make sure to use querystring module to encode the token when sending via Email.

const Persona = use('Persona')

async register ({ request, auth, response }) {
  const payload = request.only(['email', 'password', 'password_confirmation'])

  const user = await Persona.register(payload)

  // optional
  await auth.login(user)
  response.redirect('/dashboard')
}

The optional callback is invoked with the user instance just before the password verification. You can use it to check for userRole or any other property you want.

Verifies the user credentials. The value of uid will be checked against all the uids.

async login ({ request, auth, response }) {
  const payload = request.only(['uid', 'password'])
  const user = await Persona.verify(payload)

  await auth.login(user)
  response.redirect('/dashboard')
}

Verifies the user's email using the token. Ideally that should be after someone clicks a URL from their email address.

1. Removes the token from the tokens table.
2. Set user account_status = active.

async verifyEmail ({ params, session, response }) {
  const user = await Persona.verifyEmail(params.token)

  session.flash({ message: 'Email verified' })
  response.redirect('back')
}

Updates the user columns inside the database. However, if the email is changed, it performs the following steps:

Please note that this method will throw an exception if the user is trying to change the password.

1. Sets the user's account_status = pending.
2. Generates an email verification token.
3. Fires the email::changed event.

async update ({ request, auth }) {
  const payload = request.only(['firstname', 'email'])
  const user = auth.user
  await Persona.updateProfile(user, payload)
}

Updates the user's password by performing the following steps:

Make sure to have the beforeSave hook in place for hashing the password. Otherwise the password will be saved as a plain string.

1. Ensures old_password matches the user's password.
2. Makes sure the new password is confirmed.
3. Updates the user password.
4. Fires the password::changed event. You can listen for this event to send an email about the password change.

async updatePassword ({ request, auth }) {
  const payload = request.only(['old_password', 'password', 'password_confirmation'])
  const user = auth.user
  await Persona.updatePassword(user, payload)
}

Takes a forgot password request from the user by passing their uid. Uid will be matched against all the uids inside the config file.

1. Finds a user with the matching uid.
2. Generates a password change token.
3. Emits the forgot::password event. You can listen for this event to send an email with the token to reset the password.

async forgotPassword ({ request }) {
  await Persona.forgotPassword(request.input('uid'))
}

Updates the user password using a token. This method performs the following checks:

1. Makes sure the token is valid and not expired.
2. Ensures the password is confirmed.
3. Updates the user's password.

async updatePasswordByToken ({ request, params }) {
  const token = params.token
  const payload = request.only(['password', 'password_confirmation'])

  const user = await Persona.updatePasswordByToken(token, payload)
}

You can define a function inside the config/persona.js file, which returns an object of messages to be used as validation messages. The syntax is the same as Validator custom messages.

{
  validationMessages (action) => {
    return {
      'email.required': 'Email is required',
      'password.mis_match': 'Invalid password'
    }
  }
}

The validationMessages method gets an action parameter. You can use it to customize the messages for different actions. Following is the list of actions.

1. register
2. login
3. emailUpdate
4. passwordUpdate

Below is the list of events emitted at different occasions.

The entire API is driven by exceptions, which means you will hardly have to write if/else statements.

This is great, since Adonis allows managing responses by catching exceptions globally.

Raised when validation fails. If you are already handling Validator exceptions, you won't have to do anything special.

Raised when a supplied token, to verify an email or reset password with, is invalid.

At times, you may want to have custom set of rules when registering or login new users. You can override following methods for same.

The code can be added inside the hooks file or even in the registeration controller.

Persona.registerationRules = function () {
  return {
    email: 'required|email|unique:users,email',
    password: 'required|confirmed'
  }
}

Persona.updateEmailRules = function (userId) {
  return {
    email: `required|email|unique:users,email,id,${userId}`
  }
}

Persona.updatePasswordRules = function (enforceOldPassword = true) {
  if (!enforceOldPassword) {
    return {
      password: 'required|confirmed'
    }
  }

  return {
    old_password: 'required',
    password: 'required|confirmed'
  }
}

Persona.loginRules = function () {
  return {
    uid: 'required',
    password: 'required'
  }
}