<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
0D51Y00008W5cKtSAJOkta Classic EngineIntegrationsAnswered2026-04-01T09:00:20.000Z2020-05-26T18:07:28.000Z2020-05-27T12:44:14.000Z

JesseJ.06409 (Customer) asked a question.

Faster Active Directory Import?

For a given Active Directory, we can set the import schedule, and the quickest is 1 hour. Apparently some of our customers are upset that it can't be instantaneous. There isn't any way to make it shorter, or some sort of API to allow a customer to do a Import Now, is there?


  • User15851122134349081871 (North Central-Enterprise)

    I'd be interested in knowing more about the use-cases your customers have for this; sometimes we can get hung up on an assumed solution rather than working backwards from the desired outcome, and setting imports to happen continuously would probably have performance impacts. For example: is it that they want to be sure users will have Okta accounts when they first sign in? If so, Just-in-Time provisioning might achieve what you want.

    Expand Post
    • JesseJ.06409 (Customer)

      But even with JIT provisioning, they would still be unable to login until an import happens.

      • JesseJ.06409 (Customer)

        Then what could I be missing? I have "JIT provisioning" turned on as well as "Enable delegated authentication to Active Directory". But there still needs to be an import so the user shows up under "Import Results".

      • User15851122134349081871 (North Central-Enterprise)

        If you look at the first link in the two I bulleted in my previous reply you'll see that:

         

        "If delegated authentication is enabled, you do not need to import users from AD first for JIT provisioning to create Okta accounts.

         

        "If you do not have delegated authentication enabled, you must import the AD accounts first, and they must appear on the imported users list for JIT provisioning to create Okta accounts."

         

        So if your delegated authentication is correct, you don't need to import users first: Okta will create those accounts whenever a user signs in for the first time. It's only if you're not using delegated authentication that you must import them first to have JIT activate the users.

         

        Expand Post
  • k5fuw (k5fuw)

    For several years, I had similar issues with the one-hour import schedule, and because we were using a custom login page that didn't support it, just-in-time provisioning was not an option. Last year, I finally managed to talk management into retiring the custom login page in favor of the standard tenant login page, and enabled just-in-time provisioning. It has eliminated almost every complaint I had that related to scheduled imports. Newly-created AD user accounts get imported immediately if that user attempts to sign in before the scheduled import. AD account changes, including group membership changes, are imported and applied at the user's next sign in. The only thing missing is that new AD groups don't get imported until the next scheduled import (or an on-demand import).

    Expand Post
    • JesseJ.06409 (Customer)

      I don't understand. I have JIT provisioning turned on, but a user still can't login until an import happens.

  • k5fuw (k5fuw)

    The only other thing I can think of is checking the boxes to auto-confirm and auto-activate new users. We've always had those checked so I'm not exactly sure about the sequence of events, but I could see that JIT might pull in a new user from AD at login, but they might get stuck if you're not auto-confirming and auto-activating their Okta accounts.

     

    Check your System Log for events related to just-in-time provisioning (just to see if it's actually working) - enter this query:

    eventType eq "system.agent.ad.realtimesync"

     

    At least one event of this type should occur every time an AD-mastered user signs in, which indicates that the Okta AD Agent is attempting to pull the latest account info for that user from AD.

     

    Expand Post
This question is closed.
Loading
Faster Active Directory Import?