New issue
Advanced search Search tips

Issue 655960 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 571001
Owner:
Closed: Oct 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Can't login to Chromium Sync with SAML authentication

Reported by alberto....@gmail.com, Oct 14 2016

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/53.0.2785.143 Chrome/53.0.2785.143 Safari/537.36

Steps to reproduce the problem:
1. Access chrome://chrome-signin and enter my email
2. I get redirected to the SAML login page
3. Fill in authetication details
4. I get a popup saying "Uh-oh, service unavailable and sync is not enabled

What is the expected behavior?

What went wrong?
SAML authentication succeds but the sync setup fails after SAML login process.

Did this work before? Yes About 3 weeks ago

Chrome version: 53.0.2785.143  Channel: stable
OS Version: Ubuntu 16.04 and 16.10
Flash Version: 

If I initiate the sync setup from the "Settings -> Sign in" menu it still fails to setup sync after submitting the SAML login, but I get a 404 error page instead of the popup.

Sync used to work before with the same SAML-enabled account.

FWIW sync works fine with a different profile on the same browser using a personal gmail account.

Attached is the output of the chrome://signin-internals page
 
signin-internals.png
155 KB View Download

Comment 1 by pav...@chromium.org, Oct 14 2016

Cc: ew...@chromium.org
Components: Services>SignIn

Comment 2 by ew...@chromium.org, Oct 14 2016

Cc: msarda@chromium.org
Components: -Services>Sync
Labels: signin-active-bug
Owner: anthonyvd@chromium.org
Status: Assigned (was: Unconfirmed)
Anthony, you were looking into issues with SAML, right? Can you take a look at this bug? Should we dupe it against another SAML-related bug?
Mergedinto: 571001
Status: Duplicate (was: Assigned)
Yep, this looks like a dupe of  Issue 571001  and should be fixed in 54. Feel free to reopen if it's still reproducible in that version.
I'm still seeing this issue on Chromium 55.0.2883.75 (on Ubuntu 16.10)

Sign in to add a comment