...shared library of code used for our SAML (Security Assertion Markup Language) messages. This removes dependencies between our microservices and will allow us to make changes to our code faster....
...transfer skills throughout the team. It also produces high quality, maintainable code. In situations where it doesn't make sense to pair, we ensure peer review as a minimum to see...
...second step can be a code sent to a mobile phone (one of the more commonly used methods), or it can be another method such as a code communicated to...
...beta. From June onwards we’ll start to increase the pace, adding more services and allowing more people to sign in securely and conveniently with identity assurance. As always, we welcome...
...These projects are crucial in growing our understanding and improving service design. We will post about the findings and future projects on the blog. As ever, we welcome your comments....
...other purpose without your informed consent. We hope this guide will help people understand how GOV.UK Verify works. We'll welcome any comments about how we can improve it to make...
...your name, organisation and contact number to idap_procurement_2@digital.cabinet-office.gov.uk no later than 5pm on Friday, 24 October. You're also welcome to comment and ask questions by commenting on this post. ...
...welcome your views on these two posts to help us continue this work. Update: Here's a post from the Chair of our Privacy and Consumer Advisory Group, linking to...
...like GOV.UK Verify work, and how users' privacy can best be protected. We welcome the paper, and its contribution to the developing pool of knowledge and ideas about digital identity...
...the integration of their service with GOV.UK Verify. We’re still working on this guide to make sure it’s as clear and helpful as possible, and we welcome feedback from users...
