bf146c2 Merge pull request #43 from klrmn/master
cbc4fe0 fix getters

git-subtree-dir: automation-tests/browserid
git-subtree-split: bf146c230b5ea96590c25f8d55c16c57c8240744

perform rigorous validation on all API parameters, cleanup redundancy in sanitize.js and validate.js - issue #1526

Signed-off-by: Lloyd Hilaiel <lloyd@hilaiel.com>

when certifying secondary certs and the user has not confirmed their ownership of the given computer, certify with a short validity period

fix regression in keysigner - ensure non-default VAR_PATH is relayed to compute processes - issue #213

implement graceful process shutdown, and clear logging as to the reason why processes are terminating.  include winston handling of uncaught exceptions.  this all goes into a library that all of our processes use.  closes #529

in production (dev/beta/prod) use a more conventional logging format that includes timestamps.  closes #234

implement graceful process shutdown, and clear logging as to the reason why processes are terminating.  include winston handling of uncaught exceptions.  this all goes into a library that all of our processes use.  closes #529

in production (dev/beta/prod) use a more conventional logging format that includes timestamps.  closes #234

WSAPI CHANGES in preparation for new UX flows, specifically where you provide a password AFTER verifying emails.

  * stage_user no longer takes a password
  * after calling stage_user, you can poll status with user_creation_status
  * instead of 'prove_email_ownership', you call 'complete_user_creation' and provide a password
  * add_email is now 'stage_email'
  * after calling stage_email, you can poll status with email_addition_status
  * instead of 'prove_email_ownership', you call 'complete_email_addition' and provide a password
  * stage_* and complete_* calls are POST
  * *_status calls succeed continuously (not only once)

now that jwcrypto is a node module, we shall change the way that we include it (ie jwcrypto/vep rather than by relative path)

logging setup is moved into app.js for the browserid server (now common between test and prod envs).  remove it from the run.js harness

find instances of console.log() and send them to the logger instead, when running under dev harness also route to console.  issue #169