GOV.UK Verify developers: how our team works
Software developer David King gives us an insight into how the GOV.UK Verify developer team works.
Technical
Creating better acceptance criteria
Are you interested in our approach to acceptance criteria and setting the boundaries for user stories on GOV.UK Verify? Read about this - and the effect it has had on the team - in Kit Carrau’s post on the GDS …
GOV.UK Verify on the Performance Platform
From today we have started to publish performance data about GOV.UK Verify on the GOV.UK performance platform as required by Point 17 of the Digital by Default Service Standard which says: Report performance data on the Performance Platform The data is retrospective …
STORK: a practical way to access services across borders
European Union member states have been developing electronic identity (eID) schemes for some time now to allow citizens to access services safely and securely online. Many of these schemes are linked to national identity cards or schemes, whereas others involve working …
How the GOV.UK Verify technical architecture protects users' privacy, and why it's appropriate
When we designed the identity assurance architecture we wanted to protect users from identity theft and fraud, to secure their data as it is used online, and to reduce the amount of information needed from the user to a minimum. …
How we use open source code on the identity assurance programme
James Stewart has published a post about how GDS decides when it's ok not to publish source code. The identity assurance programme operates within the approach outlined by James. We do publish information about our design, but we don’t publish code …