...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...
...We should improve how often we rotate between who drives the mouse and keyboard We should investigate how we can improve our development setup to support mobbing whether through better...
...through our requirements and, in particular, thinking about the data. This resulted in a life-sized sketch of the prototype, which showed the connections between data sets and meant that everyone...
...needs. The GDS Design Principles encourage us to make things open as it makes things better and for GOV.UK Verify we want to share what we’re doing whenever we can....
...real life. With a better understanding of users’ accessibility needs, we can remove barriers - or, even better, make sure those barriers don’t exist in the first place. We learnt...
...points of the standard before going live. The GOV.UK Verify team used the criteria of the Service Standard as a tool for development throughout GOV.UK Verify’s beta phase as it...
