Releasing safe and useful code for GOV.UK Verify
...to why this cannot be done for specific subsets of the source code). This post is about how we’re going to open up our code. It explains what we’ve opened...
...to why this cannot be done for specific subsets of the source code). This post is about how we’re going to open up our code. It explains what we’ve opened...
...GOV.UK Verify in accordance with the Technology Code of Practice, the Identity Assurance Principles and the Code of Interoperability. We’ll need to adapt these procedures to work for local government...
...The codebase for GOV.UK Verify is mainly java microservices at the backend. At the frontend we use Jade as our templating language. However, we’re currently rebuilding the frontend of the...
...published We made the first small step towards opening up our codebase this year when we published a small module of code. There is a lot more to come in...
...in our codebase and allow us to deploy new code faster Things we plan to do next Over the Christmas period we have a change freeze and are not deploying...
...app to generate a security code or to receive a security code on your landline phone, rather than waiting for a text to arrive, so you don’t need a mobile...
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...
...Netherlands and the BankID systems in Sweden and Norway. This paper describes how Verify test environments could work, sets out the standards expected, and shows how organisations can demonstrate they...
Last week, the GDS Identity Assurance Programme, as an acknowledged leader in the space, played host to government counterparts from Australia, Canada, Denmark, Japan, New Zealand and Sweden (sadly the...
...towards the end of last year. Reducing our technical debt There are things we need to do to the GOV.UK Verify codebase to tidy up accumulated impact of having made...