...new one. Our open source kanban Done We’ve already published some code: https://github.com/alphagov/eager-dropwizard-guice - code to make it easier to use Guice with Dropwizard https://github.com/alphagov/interaction-diagrams - visualisation of SAML messaging...
...services under the new contracts we signed earlier this year. This includes the existing companies that are transitioning on to new contractual terms, and the new companies that will be...
...any new code. Our next release of new code will be in January. Over the next 2 weeks we plan to: prepare our next A/B test of the introduction pages...
...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...
...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...
...lab. The new content introduces the idea that GOV.UK Verify ‘is a new scheme to fight the growing problem of online identity theft’. The change has had a positive impact...
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...
...for the new certified companies joining GOV.UK Verify soon, for example we will need to change some of the questions to reflect the different methods new providers will be offering....
...Combining a tried and tested framework with a brand new programming approach The new frontend is being built using Ruby on Rails. One of the main draws for using Rails...
...the new providers on board. We’re also being transparent with our performance data, publishing new statistics weekly to the Performance Platform. Objectives for live Moving from beta to live is...
