Table of contents

• Ally custom driver boilerplate
  • Getting started
  • How is the code structured?
    • OktaDriverAccessToken
    • OktaDriverScopes
    • OktaDriverConfig
    • OktaDriver
  • Development checklist
  • Testing the driver
  • Release checklist
  • FAQ's
    • How do I define extra params during redirect?
    • How do I define extra fields/params for the access token request?
  • Share with others

Ally custom driver boilerplate

A boilerplate for creating custom AdonisJS ally drivers

This repo serves as a starting point to create your custom OAuth2 drivers for AdonisJS ally.

The boilerplate is tailored to create one driver per project and publish it as a package on npm.

Getting started

Following are the steps to get started.

• Fork this repo and then clone it on your local machine.

• Install all the dependencies using npm or yarn (whatever you prefer).

• Open package.json file and update the package name, description and the adonisjs configuration block.

  {
    "name": "package-name",
    "description": "",
    "adonisjs": {
      "types": "package-name",
      "providers": ["package-name"]
    }
  }

How is the code structured?

The code for the driver is inside the src directory. Make sure to change the OktaDriver directory name to the name of the driver.

The driver implementation is mainly driven by the config, except the user and the userFromToken methods. Both of these methods are specific to the Oauth provider, and hence you have to implement them yourself.

The src/OktaDriver/index.ts file has the following exports.

OktaDriverAccessToken

The type defines the properties that exist on the access token returned by your driver. You must read your OAuth provider documentation and list all the properties here.

Do not change the pre-defined token and bearer properties.

export type OktaDriverAccessToken = {
  token: string
  type: 'bearer'
}

OktaDriverScopes

Define a union of driver scopes accepted by your OAuth provider. You can check out the official implementations to see how they are defined.

OktaDriverConfig

The type defines the configuration options that your driver expects. It must specify the following mentioned properties, along with any additional properties your driver needs to be functional.

export type OktaDriverConfig = {
  driver: 'OktaDriverName'
  clientId: string
  clientSecret: string
  callbackUrl: string
  authorizeUrl?: string
  accessTokenUrl?: string
  userInfoUrl?: string
}

OktaDriver

The driver implementation is a standard TypeScript class that extends the base Oauth2Driver class. The base driver class enforces you to define the following instance properties.

• authorizeUrl is the URL for the redirect request. The user is redirected to this URL to authorize the request. Check out provider docs to find this URL.
• accessTokenUrl is used to exchange the authorization code for the access token. Check out provider docs to find this URL.
• userInfoUrl is used to make a request for getting the user profile information
• codeParamName is the query string parameter for reading the authorization code after redirecting the user back to the callback URL.
• errorParamName is the query string parameter for finding the error after redirecting the user back to the callback URL.
• stateCookieName is the cookie name for storing the CSRF token (also known as the state). Make sure the cookie name does not collide with other drivers. A safer option is to prefix your driver name to the oauth_state keyword.
• stateParamName is the query string parameter name for setting the state during the authorization redirect.
• scopeParamName is the query string parameter name for sending the scopes during the authorization redirect.
• scopesSeparator is the character to use for separating multiple parameters.

Development checklist

• I have renamed all OktaDriver references to a more meaningful driver name inside the src/OktaDriver/index.ts file.
• I have renamed the OktaDriverProvider inside the providers/index.ts file.
• I have updated the driver name in the Ally.extend method call inside the providers/index.ts file.
• I have defined the authorizeUrl class property.
• I have defined the accessTokenUrl class property.
• I have defined the userInfoUrl class property.
• I have defined the codeParamName class property.
• I have defined the errorParamName class property.
• I have defined the stateCookieName class property.
• I have defined the stateParamName class property.
• I have defined the scopeParamName class property.
• I have defined the scopesSeparator class property.
• I have implemented the accessDenied class method.
• I have implemented the user class method.
• I have implemented the userFromToken class method.
• I have updated the standalone.ts file to export the renamed driver file name.

Testing the driver

You can test the driver by installing it locally inside your AdonisJS application. Following are the steps you need to perform.

• Compile the TypeScript code to JavaScript using the npm run build script.

• cd into your AdonisJS project and install the package locally using npm i path/to/your/driver/package.

• Run node ace configure <package-name>. The configure command needs the package name and not the package path.

• Inform typescript about your driver by defining a mapping inside the contracts/ally.ts file.

  import { OktaDriverConfig, OktaDriver } from 'ally-custom-driver/build/standalone'
  
  interface SocialProviders {
    OktaDriver: {
      config: OktaDriverConfig
      implementation: OktaDriver
    }
  }

• Define the config inside the config/ally.ts file.

• And now you can use your driver like any other inbuilt driver.

Release checklist

Make sure to finish the following tasks before releasing your package.

• I have renamed the name and description properties inside the package.json file.
• I have renamed the adonisjs.types and adonisjs.providers properties to use the package name inside the package.json file.
• I have updated the post-install instructions inside the instructions.md file.
• I have updated the adonisjs.env property inside the package.json file to use the correct driver name for environment variables.

FAQ's

How do I define extra params during redirect?

You can configure the redirect request by implementing the configureRedirectRequest method on the driver class. The method is already pre-defined and commented out.

protected configureRedirectRequest(request: RedirectRequest<OktaDriverScopes>) {
  request.param('key', 'value')
}

How do I define extra fields/params for the access token request?

You can configure the access token request by implementing the configureAccessTokenRequest method on the driver class. The method is already pre-defined and commented out.

protected configureAccessTokenRequest(request: ApiRequest) {
  // Request body
  request.field('key', 'value')

  // Query param
  request.param('key', 'value')
}

Share with others

Are you excited about sharing your work with others? Make sure to submit your package to the awesome-adonisjs repo.