How we use open source code on the identity assurance programme
...up to date thinking following our private beta. Using an open standard such as SAML 2.0 allows departments working with us to use a variety of products, including open source...
...up to date thinking following our private beta. Using an open standard such as SAML 2.0 allows departments working with us to use a variety of products, including open source...
GOV.UK Verify has been in public beta since 14 October. One of the services we've been working with is rural payments. We’ve been working with the service and with our...
...will not be joining the public beta. We’ve blogged separately about Mydex’s contribution to the development of GOV.UK Verify and their important ongoing role in the development of identity assurance...
GOV.UK Verify allows people to choose from a list of certified companies. Before certified companies can join the GOV.UK Verify public beta, they must demonstrate that they can deliver services...
...public beta, and was solely responsible for the user support function for several months. One of the benefits of conducting service design in phases - alpha, beta, live - is...
...a wider range of disciplines than would be needed for other more straightforward services. Overall we have approval and funding for more than 100 people as we move from Beta...
...we can share our research and find out the easiest way for a user to understand or achieve something. Point 1 in the Standard says: Understand user needs. Research to...
I posted recently about our progress towards taking GOV.UK Verify from beta to live. This is a short update to let you know that we’ve now passed our Digital by...
...points of the standard before going live. The GOV.UK Verify team used the criteria of the Service Standard as a tool for development throughout GOV.UK Verify’s beta phase as it...
...now expect to happen later in the year. We now have better data and can make better quality estimates than before. Since last time In order to estimate how many...