...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...
...60 732 The Post Office e-mail: myprofilehelpdesk@postoffice.co.uk Telephone: 0330 60 60 733 SecureIdentity e-mail: help@secureidentity.co.uk Telephone: 0330 100 0103 Barclays Telephone: 0333 202 7479 (English) or 0333 202 7450 (Welsh)...
...representing GOV.UK Verify for a workshop on the theme of identity. This was also attended by representatives from the other D5 countries: Estonia, Israel, New Zealand and South Korea. The...
...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...
...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...
...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...
...migrated infrastructure providers previously on the project as we moved from alpha to private beta. Public Key Infrastructure We also run a PKI to enable secure communication between the entities...
...aren’t able to complete the second step. At the start of our public beta, the only way to complete the second step was to receive an SMS code on your...
...it better for end users, since our last update we’ve: completed an A/B test which looked at a new way of describing GOV.UK Verify based on our research in the...
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...
