On 30/01/2014 2:06 AM, Stefan Arentz wrote:
>
> On Jan 29, 2014, at 1:40 AM, Ryan Kelly <rfkelly at mozilla.com> wrote:
>
>> We have also deployed a matching environment to the final production URL:
>>
>> https://token.services.mozilla.com/1.0/sync/1.5
>
> Ryan are you sure this works in combination with
> https://api.accounts.firefox.com/ ?
It should work. They're only tied by the standard BrowserID
verification process, and Nick reports that this combo works for him
from inside the android sync code.
> When I create a new (and verified) account on api.accounts, the new
> production token server tells me I am unauthorized.
My first guess would be some sort of clock-skew-related failure. The
401 response from the tokenserver should have a JSON body with
additional details, what does it return?
What method are you using to perform this login sequence? I'll try to
replicate and track down the error.
Cheers,
Ryan
_______________________________________________
Sync-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/sync-dev
