- 01 Jul, 2019 3 commits
-
-
MickeyMoz authored
-
Christian Sadilek authored
-
MickeyMoz authored
-
- 28 Jun, 2019 1 commit
-
-
MickeyMoz authored
-
- 27 Jun, 2019 2 commits
-
-
Sawyer Blatz authored
Co-authored-by:
NotWoods <contact@tigeroakes.com>
-
MickeyMoz authored
-
- 26 Jun, 2019 2 commits
-
-
Sebastian Kaspari authored
-
MickeyMoz authored
-
- 25 Jun, 2019 4 commits
-
-
Tiger Oakes authored
-
MickeyMoz authored
-
Denys M authored
-
Denys M authored
-
- 24 Jun, 2019 1 commit
-
-
Sebastian Kaspari authored
-
- 21 Jun, 2019 2 commits
-
-
Sebastian Kaspari authored
-
MickeyMoz authored
-
- 20 Jun, 2019 1 commit
-
-
MickeyMoz authored
-
- 18 Jun, 2019 1 commit
-
-
MickeyMoz authored
-
- 14 Jun, 2019 8 commits
-
-
Tiger Oakes authored
-
Sebastian Kaspari authored
-
MickeyMoz authored
-
Sebastian Kaspari authored
-
Sebastian Kaspari authored
-
Sebastian Kaspari authored
-
Sebastian Kaspari authored
-
Sebastian Kaspari authored
-
- 13 Jun, 2019 1 commit
-
-
MickeyMoz authored
-
- 12 Jun, 2019 3 commits
-
-
MickeyMoz authored
-
Sebastian Kaspari authored
-
Gabriel Luong authored
Closes #3344: Add getProvidedDefaultSearchEngine to SearchEngineManager to get the provided default search engine.
-
- 11 Jun, 2019 8 commits
-
-
Sebastian Kaspari authored
-
James Hugman authored
-
Sebastian Kaspari authored
-
Grisha Kruglov authored
-
Grisha Kruglov authored
This calls a new FirefoxAccount.onAuthTokenError method after encountering auth errors, which clears out internal token caches in the fxalib. Right after, we attempt to recover. It's possible our access token simply expired. We do so by trying to obtain a new access token. If that fails, we've certainly hit an authentication problem and need user intervention to recover. Otherwise, we proceed back into authenticated states. Finally, if we are in trouble and hit a real authentication problem, clear out any and all mention of the old account data. Currently there's a caching bug which means we'll re-use a bad access token during a device refresh even after re-authenticating, and this works around that bug. Additionally, this sneaks in one more change: requesting a "profile" scope is no longer necessary from the application's point of view. This change is backwards compatible, since passed scopes array is treated as a set. This change was necessary to future-proof our token recovery flow. With it in place, we can be certain that we'll always have the scope with which we're trying to recover.
-
Arturo Mejia authored
-
MickeyMoz authored
-
Sebastian Kaspari authored
-
- 10 Jun, 2019 3 commits
-
-
Sebastian Kaspari authored
-
Sawyer Blatz authored
-
MickeyMoz authored
-