...a Windows phone were offered the alternative options of receiving a security codes via landline or SMS. One of the certified companies recently launched a Windows phone app, meaning those...
...effectively. To continue keeping GOV.UK Verify available and secure we’ve: started automating lengthy steps in our process when releasing code to our live environment upgraded lots of applications and libraries...
...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...
...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...
The GOV.UK Verify technical delivery team recently started building a new version of our frontend application (not the design - that will look the same as it does now). We...
...pages (e.g. clicks made on links) and extra tagging code called custom variables which enabled us to segment the data. We also added an extra step into the process: when...
...Commissioner’s Code of Practice for Privacy Impact Assessments provides an excellent proposed methodology for a PIA, which was used as a starting point for the review of GOV.UK Verify. Conducting...
...skipping through sections that the screen reading software identifies using the header tags in the code. However, we realised that some of the pages in GOV.UK Verify don’t use headers...
