Issue metadata
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 descriptionUserAgent: 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:
,
May 9 2018
Screenshot which is shown to the user after login
,
May 9 2018
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.
,
May 9 2018
Lutz, could you please take a look/triage?
,
May 10 2018
,
May 11 2018
+jdufault, +alemate Assigning to Alex since this appears to be an issue with the new login UI.
,
Aug 3
This bug has an owner, thus, it's been triaged. Changing status to "assigned". |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by ibezmenov@chromium.org
, May 8 2018