<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D51Y00009zbcd3SAAOkta Classic EngineSingle Sign-OnAnswered2025-06-06T09:00:09.000Z2020-11-25T10:44:46.000Z2021-11-18T15:30:08.000Z
  • User15730068971817219468 (Vendor Management)

    My name is Alexandru from Okta Support.

    Right now,  Passwordless Authentication flow, although not explicitly documented, is not currently supported for Chrome OS devices.

    As you do have factor sequencing enabled, this will not work.

     

    • Hi Alexandru,

      Just to clarify login to chromebook via OKTA is not supported.

      Reards,
      Giri
      Expand Post
      • lee.tschetter (Okta, Inc.)

        Logging in to Chromebooks is fully supported and many customers are doing this in production. If the Google Workspace account that is being used to sign in to ChromeOS is federated then the user will be sent to Okta during the ChromeOS login process.

  • User15730068971817219468 (Vendor Management)

    When Factor Sequencing is enabled, users will be stuck after inserting username because is not supported by ChomeOS devices.

    There is already an idea suggested on Okta Ideas: https://ideas.okta.com/app/#/case/110072

    As this idea has already been implemented in our Okta Ideas, the only option at hand would be for us to vote that option so that our Engineering Team could consider working on it.

     

    Expand Post
    • lee.tschetter (Okta, Inc.)

      The issue with the login screen not progressing with factor sequencing enabled can by worked around by adding a routing rule for "other" platforms (ChromeOS is not listed as a platform). This rule does not need to do anything, it just needs to exist so that the default routing rule does not trigger. The issue with factor sequencing only exists when the default routing rule runs.

      Expand Post
      • f07p2 (f07p2)

        Just replying here to say thanks for posting this fix- it helped us avoid a potentially huge problem with our Chrome OS fleet. 🙏

      • fncjo (fncjo)

        We're running into the same issue (users stuck after entering the username on the Okta prompt on the ChromeOS device login screen), but we didn't get it working after adding that "routing rule" for "other" platforms. Do we have to add a (dummy) "identity provider" in the Identity Providers page if we don't already have another identity provider configured (a little loathe to do this, since we don't actually use any other identity providers).

        Expand Post
      • lee.tschetter (Okta, Inc.)

        James was successful with it just 3 days ago, so there is something different between your environments. I am not sure if there is a new feature flag that once again breaks the ChromeOS login process, but I do know for certain that disabling factor sequencing resolves the issue.

      • f07p2 (f07p2)

        I'll clarify to avoid any confusion;

        • We had several IDP routing rules in place above the default rule. These were being used whilst we migrated batches of users from a different IdP to Okta and at the time we had no idea Factor Sequencing would cause Chromebook issues. One of the rules is shown below and matches what Lee describes:
          Image is not available
          With this setup our Chromebooks were authenticating with Okta as IdP just fine.
        • When we had completed the migration from the old IdP, we disabled all the routing rules except default. This is where we ran into trouble and could not proceed past the username entry for Chromebook logins. Factor Sequencing isn't necessary for us, so rather than reinstate routing rules we just disabled the feature altogether.
        Expand Post
10 of 16
This question is closed.
Loading
OKTA SSO - Chromebook