QA/Browser Technologies/Services/Releases/BrowserID 08252011

Information

• Train 4: 08-25-2011

Links

• Bugs/Issues: https://github.com/mozilla/browserid/issues
• Test Plan: https://wiki.mozilla.org/QA/BrowserID/TestPlan
• Beta Server: https://diresworb.org
• Beta Client: http://beta.myfavoritebeer.org

Deployment Ticket

• bug 682045 - QA and deploy BrowserID train-2011.08.25 to production

Resolved/Closed Issues

• Verified by QA
• [BrowserID issue 191] : manage page date format
• [BrowserID issue 195] : manage page button only displayed if user is currently authenticated
• [BrowserID issue 181] : manage page emails are synced on page open
• [BrowserID issue 199] : fix new email addresses added not being synced on client
• [BrowserID issue 215] : more than one email address can be added per dialog lifespan
• verifyier no longer verifies assertions issued by another server.
• [BrowserID issue 203] : Please use the HTML5 email input field
• [BrowserID issue 219] : set_key slow in production with google chrome

• No specfic QA testing is needed
• [BrowserID issue 125] : create tools for load simulation and capacity estimation.
• [BrowserID issue 183] : beginning unit/functional tests for front end
• [BrowserID issue 183] : front end refactor to facilitate unit/functional tests and UX iteration
• [BrowserID issue 184] : Simplify the showing of the error dialogs.
• users must now verify account ownership before attempting a key sync.
• wsapi_client created for clients needing programatic access to wsapi.
• harden set_key against duplicate keys.
• upgrade to bcrypt 0.2.4.
• [BrowserID issue 206] : minify include.js by default

Opened Bugs/Issues

• [BrowserID issue 202] : there have been some user complaints that confirmation emails aren't received
• [BrowserID issue 204] : support bcrypt work factor update
• [BrowserID issue 205] : write up a wiki page about why we are using node.js
• [BrowserID issue 208] : determine size requirements for mysql with 1M active
• [BrowserID issue 209] : audit all SQL queries performed and ensure they hit indicies
• [BrowserID issue 210] : determine max QPS on reasonable VM
• [BrowserID issue 211] : figure out distributed mysql configuration
• [BrowserID issue 212] : determine default bcrypt work factor
• [BrowserID issue 213] : ensure that the verifier can saturate multiple cores
• [BrowserID issue 214] : move to socketlabs for email delivery
• [BrowserID issue 216] : /ws_api/csrf response is producing a syntax error
• [BrowserID issue 217] : Change all wsapi calls to return JSON response
• [BrowserID issue 218] : validating an email a second time causes undecipherable error.
• [BrowserID issue 207] : All static resources should be gzipped and served with proper cache headers
• [BrowserID issue 222] : incorrect initial authentication is not displaying error message.
• [BrowserID issue 232] : New accounts: Login string and logout link are "invisible" on beta.myfavoritebeer.org
• [BrowserID issue 233] : Opera on Mac: Tabbed UI vs. pop-up results in inability to log into beta.myfavoritebeer.org
• [BrowserID issue 234] : Would be nice to have date/time stamps in BrowserID logs

Notes