To prepare for the Document Checking Service (DCS) pilot we built out several new capabilities in the service and published our first API documentation powered by user testing.
The GOV.UK Verify team at GDS needed to make sure data was protected when being shared with the eIDAS regulation framework. Here’s how they did it.
The Digital Identity team at GDS has updated its Good Practice Guide on authentication and Service Manual content on checking users' identities. The new guidance provides users with clearer, more up-to-date information.
The GOV.UK Verify team has changed the way its frontend is deployed. We take a deep dive into the technical challenges and how the load balancing changes give users a better experience.
The standards that underpin GOV.UK Verify have always been open but we started coding as a private project. Here’s a recap of our journey to coding in the open.
At GOV.UK Verify we take users’ security very seriously. Online security is constantly changing, and we need to be up to date at all times. We regularly update the service’s frontend to ensure it’s running the most secure and recent …
You may have heard, rule number one for us at Government Digital Service (GDS) is: “always start with user needs”. We do user research. Lots of it. GOV.UK Verify recently completed their 100th round of user research, and they’re not …
Over the past year at GDS, we’ve been working hard to create a strong technology community. Recently we took a day out of the office together. The GDS Technology community is pretty big – just over 90 civil servants and …
On GOV.UK Verify, we’ve adopted a micro-services approach to our architecture
Web server configuration can be tricky to get right. Applications like nginx or apache are flexible and powerful. However this flexibility can result in configuration which is hard to understand, hard to maintain, and easy to accidentally break. On the …
If you’re interested in jobs in this field, check out all open opportunities on the GDS careers site.