Table of contents

Development steps

This is a summary of the technical steps involved in connecting your service to GOV.UK Verify. This summary will help set a roadmap for your team’s development work.

Before starting development, you should have already decided how to:

Local development

In this phase, you’re setting up the Verify Service Provider to generate authentication requests and translate responses.

Make sure your service correctly uses the Verify Service Provider to handle:

You should also test that your service can handle your use case for data from the GOV.UK Verify Hub.

For a detailed description of the Verify Service Provider’s API, see:

End-to-end testing

In this phase, you’re doing end-to-end testing of user journeys in a secure test environment. The environment known as ‘Integration’ contains a full-scale deployment of the GOV.UK Verify Hub.

To access the test environment:

  1. Obtain signed certificates for the test environment.
  2. Fill in the 'Request access to an environment’ form.
  3. Configure the VSP for the test environment.

Once connected to the test environment, run end-to-end testing on all your user journeys.

Go live

To access the production environment:

  1. Obtain signed certificates for the production environment.
  2. Fill in the 'Request access to an environment’ form.
  3. Configure the VSP for the production environment.

You’re ready to connect your Verify Service Provider to the production environment.

Maintenance

To keep your service connected to the GOV.UK Verify Hub, your certificates must be up to date. Make sure you update your certificates when they are due to expire.

Make sure you’re running an up-to-date release of the Verify Service Provider.

This page was last reviewed on 12 April 2019. It needs to be reviewed again on 12 August 2019 by the page owner #verify-developers .
This page was set to be reviewed before 12 August 2019 by the page owner #verify-developers. This might mean the content is out of date.