Today we're publishing two posts that explain what we're doing to protect users' privacy when they use GOV.UK Verify. For the last three years we've been working with our Privacy...
...for the new certified companies joining GOV.UK Verify soon, for example we will need to change some of the questions to reflect the different methods new providers will be offering....
...companies refer to data sources today are: validating details provided by users about their passport or driving licence against official government records through the document checking service. drawing on data...
...Cain (@mcaino) July 15, 2016 Today we held the first of 2 discovery days to examine how local authority taxi licensing, concessionary travel and parking permit services might be improved...
The identity assurance service will allow users to sign in to government services and prove their identity quickly, safely and privately. Today an important part of the service, the 'hub',...
...Combining a tried and tested framework with a brand new programming approach The new frontend is being built using Ruby on Rails. One of the main draws for using Rails...
...the new providers on board. We’re also being transparent with our performance data, publishing new statistics weekly to the Performance Platform. Objectives for live Moving from beta to live is...
...step such as having a one-off code sent to your mobile phone or generating a code in an authentication app. Therefore, if your information is lost or compromised it will...
...to their newer versions so we continue to run the most up-to-date and secure code Things we plan to do next In the coming 2 to 3 weeks we expect...
...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...
