[Desktop-packages] [Bug 1637957] Re: Chromium not working with SAML authentication

2017-01-20 Thread Alberto Donato
Sync is now working again with SAML. ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Fix Released -- 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

[Desktop-packages] [Bug 1637957] Re: Chromium not working with SAML authentication

2017-01-19 Thread Alberto Donato
** Changed in: chromium-browser (Ubuntu) Status: Triaged => Fix Released ** Changed in: chromium-browser (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in

[Desktop-packages] [Bug 1637957] Re: Chromium not working with SAML authentication

2017-01-13 Thread Patrick Noland
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

[Desktop-packages] [Bug 1637957] Re: Chromium not working with SAML authentication

2017-01-13 Thread Chad Miller
Patrick, we're not changing the keys back. It's impossible. The old keys were abused by someone and we lost Google API access. We have to fix this another way. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu.

[Desktop-packages] [Bug 1637957] Re: Chromium not working with SAML authentication

2017-01-13 Thread Alberto Donato
** Description changed: - 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). + Sync login is failing with SAML authentication. See - Apparently this is fixed in release 54,

[Desktop-packages] [Bug 1637957] Re: Chromium not working with SAML authentication

2017-01-13 Thread Patrick Noland
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:

[Desktop-packages] [Bug 1637957] Re: Chromium not working with SAML authentication

2016-11-04 Thread Alberto Salvia Novella
** Changed in: chromium-browser (Ubuntu) Importance: Undecided => Medium ** Changed in: chromium-browser (Ubuntu) Importance: Medium => High ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of

[Desktop-packages] [Bug 1637957] Re: Chromium not working with SAML authentication

2016-10-31 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: chromium-browser (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu.