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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1637957 Title: Chromium not working with SAML authentication To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1637957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
