Skip to main content

Docker Hub SSO Overview

We have a Docker Business Account.

This account is setup with an organisation called HMCTS.

The account has been configured to enable single sign on to Docker accounts with Entra ID.

The service principal and secret are created by a GitHub repo and pipeline called docker-hub-sso.

The pipeline will run automatically when a change is merged.

The secret has been configured to be rotated by the pipeline every 335 days which means that when there is less than 30 days until the secret expires, running the pipeline will renew it.

This should line up with our daily checks for service principal secrets which start notifying us about secrets that will expire in the next 30 days.

When that notification comes through to the daily checks, you can run the pipeline to renew the secret.

The secret is stored in a keyvault where you can retrieve it to enter it into the docker settings page.

Updating the client secret in docker

Login to the docker hub as an administrator.

Go to the settings page for the organisation and then go to Security.

Edit the single sign on connection and click Next until you reach the page where you can enter the secret.

Enter the secret value and click Next and eventually Save.

Who has admin access?

  • Enda Kelly
  • Felix Eyetan
This page was last reviewed on 16 May 2025. It needs to be reviewed again on 16 November 2025 by the page owner platops-build-notices .
This page was set to be reviewed before 16 November 2025 by the page owner platops-build-notices. This might mean the content is out of date.