...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...
...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...
...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....
...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...
...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...
...and keyboard while the rest of the mob act as ‘navigators’ by suggesting what source code needs to be produced. Not everybody will be part of the mob at all...
...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...
...covering security, Agile methodologies, open source code and more. The process was resource-intensive but it helped to focus the team on the requirements of the live assessment and proved a...
