Use GOV.UK One Login
All public facing services which require users to prove their identity and login must use GOV.UK One Login.
To meet this commitment as part of Digital and Data function’s strategic commitments your plans must show how you will use GOV.UK One Login if applicable. This includes single sign-on, digital identity, and GOV.UK accounts.
Each central government organisation has been asked to agree a date with GDS when they will adopt GOV.UK One Login services. You should check what your organisation has agreed with GDS.
This strategic commitment requires projects to not commit to new long term (longer than 12 months) contracts with digital identity providers for functionality which enables individuals to verify their identity.
Architectural decisions should allow the simple future adoption of Government One Login by aligning with the proposed identity flow and architecture as outlined in how GOV.UK One Login works.
This strategic commitment does not apply to health organisations with the exception of the Department for Health and Social Care (DHSC)
If you’re going through the spend control process you must explain how you’re meeting this commitment if your spend request has been rated high on the risk and importance framework or has an assurance rating of ‘control’.
Answering ‘no’ will not lead to an automatic rejection and you will need to explain why your spend cannot align to the commitment.
Last updated 6 March 2024 + show all updates
-
Reducing the length of allowed contracts with digital identity providers from 24 months to 12 months.
-
First published.