...our service, i.e. infrastructure code We see little potential for re-use of this area of our codebase, and it currently contains sensitive information (for example, which users have access to...
...increase our current usage of the public GDS repository in the coming months. Logging and monitoring For logging and monitoring our systems use elasticsearch, logstash and kibana. We also use...
...whole service transformation, to working services in private beta at each local authority. Councils interested in working with us can use our discovery research on concessionary travel and parking permits...
...15,000 different code commits this year - that’s 15,000 different changes to GOV.UK Verify to improve it for users and get it ready to go from beta to live in...
...to protect you against your credentials being stolen or compromised. The second step means that even if someone steals your username and password, they can’t easily use them because they...
...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 increasingly as it progresses from beta to live because it’s secure, straightforward and meets the needs of their users. To improve GOV.UK Verify and make it better for...
...Our user research team carry out at least fortnightly user research in our lab with users of a variety of demographics and digital skills, and also in users’ homes as...
...government to adopt GOV.UK Verify increasingly as it progresses from beta to live because it’s secure, straightforward and meets the needs of their users. To improve GOV.UK Verify and make...
Point 9 of the Digital by Default Service Standard says: Use open standards and common government platforms where available. GOV.UK Verify doesn’t just use open standards - we have helped...
