New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 839887 link

Starred by 4 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug-Regression



Sign in to add a comment

SAML SSO not functioning properly on new sign in

Reported by sam.kee...@gmail.com, May 4 2018

Issue description

UserAgent: Mozilla/5.0 (X11; CrOS x86_64 10643.0.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3417.0 Safari/537.36
Platform: 10643.0.0 (Official Build) canary-channel samus

Steps to reproduce the problem:
Sign into Chrome OS using an account with a SAML SSO, such as OneLogin, where the configuration is set to pass the session through.

What is the expected behavior?
Sessions are passed through properly.

What went wrong?
Session seems to not be fully passed through. Account name will be missing, chrome sync doesn't work, and the user is prompted to sign out and back in to fix chrome sync, which does not work.

Clicking the option to use webui login does work, but I am asked to file this bug when clicking it.

Note that if your account is in the broken state from this, using the webui login does fix the issue.

Did this work before? Yes 67

Chrome version: 68.0.3417.0  Channel: canary
OS Version: 10643.0.0
Flash Version:
 
Labels: Needs-Feedback
I was not able to reproduce it using the following accounts with a SAML SSO: Okta, ADFS. Chrome sync works properly, the user is not prompted to sign out.

Chrome: 68.0.3419.0 dev
Chrome OS: 10646.0.0 dev-channel coral

Could you please provide more information about this issue (screenshots, debug-logs, etc.).
Screenshot which is shown to the user after login
Screenshot 2018-05-09 at 9.44.32 AM.png
13.3 KB View Download
Here are the debug logs, from a ThinkPad 13 running dev 68.0.3417.0.

The SAML session is not passed through, though the password is.
debug-logs_20180509-094649.tgz
1.3 MB Download
Cc: ljusten@chromium.org ibezmenov@chromium.org
Labels: -Needs-Feedback
Status: Untriaged (was: Unconfirmed)
Lutz, could you please take a look/triage?
Cc: atwilson@chromium.org pelets...@chromium.org
Labels: Enterprise-Triaged
Owner: ljusten@chromium.org
Cc: alemate@chromium.org jdufault@chromium.org
Owner: alemate@chromium.org
+jdufault, +alemate

Assigning to Alex since this appears to be an issue with the new login UI.
Status: Assigned (was: Untriaged)
This bug has an owner, thus, it's been triaged. Changing status to "assigned".

Sign in to add a comment