WSAPI CHANGES in preparation for new UX flows, specifically where you provide...
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)
Showing
- browserid/lib/db_json.js 1 addition, 1 deletionbrowserid/lib/db_json.js
- browserid/lib/db_mysql.js 2 additions, 2 deletionsbrowserid/lib/db_mysql.js
- browserid/lib/wsapi.js 150 additions, 107 deletionsbrowserid/lib/wsapi.js
- browserid/tests/ca-test.js 1 addition, 1 deletionbrowserid/tests/ca-test.js
- browserid/tests/cert-emails-test.js 1 addition, 14 deletionsbrowserid/tests/cert-emails-test.js
- browserid/tests/forgotten-email-test.js 5 additions, 9 deletionsbrowserid/tests/forgotten-email-test.js
- browserid/tests/list-emails-wsapi-test.js 4 additions, 6 deletionsbrowserid/tests/list-emails-wsapi-test.js
- browserid/tests/password-length-test.js 25 additions, 15 deletionsbrowserid/tests/password-length-test.js
- browserid/tests/registration-status-wsapi-test.js 33 additions, 22 deletionsbrowserid/tests/registration-status-wsapi-test.js
Loading
Please register or sign in to comment