This broke as a result of http://bazaar.launchpad.net/~chromium-team
/chromium-browser/yakkety-working/revision/1271
The solution is to change the API keys back to their previous values.
The new key isn't trusted for the purposes of an endpoint used in the
SAML auth flow.
** Branch linked: lp:~chromium-team/chromium-browser/yakkety-working
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1637957
Title:
Chromium not working with SAML authentication
Status in chromium-browser package in Ubuntu:
Triaged
Bug description:
In Chromium 53 (tested on Xenial and Yakkety) sync setup fails if the
account login goes through SAML authentication (the setup fails after
a successful SAML login).
Apparently this is fixed in release 54, see
https://bugs.chromium.org/p/chromium/issues/detail?id=655960 and
https://bugs.chromium.org/p/chromium/issues/detail?id=571001 for
details about the bug.
Would it be possible to SRU the new version?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1637957/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
