Let's try dev-fxacct for this question. -R
On Sun, Jun 25, 2017 at 10:34 AM, Chris Tybur <thisis...@gmail.com> wrote: > Gabriel: > > Thanks for the suggestion. I was hoping to avoid having to incorporate an > entirely new way of doing the authentication, if possible. > > I should also mention that what I had working before April was to POST to > account/login, then I'd receive an email with a link asking to verify my > identity. I'd manually copy that link from the message into a page in my > app, then that page would POST to recovery_email/verify_code with the code > in the link, along with a token obtained earlier. And all was well. I just > need to know what is different about that process. > > Chris > > I have a web app that uses the Firefox Account login API to authenticate my >> account, obtain Sync storage encryption keys, then pull down my sync'ed >> bookmarks. Around April the login stopped working and started returning >> "The request was blocked for security reasons". I see at >> https://github.com/mozilla/fxa-auth-server/blob/master/ >> docs/api.md#post-accountlogin that the login API seems to have some new >> query params and payload data. >> >> Is this new data and the process documented somewhere? I'd like to be able >> to adjust my code to call the API correctly. >> >> Chris >> >
_______________________________________________ Sync-dev mailing list Sync-dev@mozilla.org https://mail.mozilla.org/listinfo/sync-dev
