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:
Alright, I'll look into updating the whitelist to reflect the new keys.
--
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
2 matches
Mail list logo
