<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
0D51Y00006CKp3qSADOkta Classic EngineSingle Sign-OnAnswered2026-04-01T09:00:20.000Z2019-04-30T22:16:51.000Z2019-05-03T16:53:34.000Z

MichaelC.84328 (Customer) asked a question.

For service account in OU excluded from import to Okta, how can I add that okta account and assign an APP?

For service account in Active Directory OU that excluded from import to Okta, how can I add import or add that to Okta account and assign an APP, so that account can access app via Okta SSO (SAML)?


  • For a user to be imported from AD to Okta, whether a service account or any other, it must be in an OU connected to Okta. Any OU not connected to Okta will not be scanned for users. You will need to either connect the existing OU to Okta, or move the user object for the service account in AD to an OU that is connected to Okta.

     

    Once the user is in an OU connected to Okta, you will be able to import them into Okta and create a corresponding user account there. Once the account is in Okta, you can proceed to assign apps.

    Expand Post
    • MichaelC.84328 (Customer)

      Did you just send me a repeat of the earlier advice? I did as instructed yesterday (I had figured that out before your reply), but STILL have the Okta sign-in failing for that account, with “NOT_SPECIFIED” error in the Okta logs.

      Meanwhile, on my scheduled support call with Sergiu Costea at Okta this afternoon, he indicated that, because this account in AD was restricted to login to only given workstations, the Okta login would fail unless from that computer; I did that, but my testing has disproved that theory (account can login to workstation but not to Okta), so looking for more help…

      Michael Cazier
      Sr. Systems Administrator
      T: 925.227.7272
      M: 415.361.8849
      Michael.Cazier@elliemae.com
      www.elliemae.com<http://www.elliemae.com>


      [EM_family_sig_NOV2017_ALT.jpg]<
      http://www.elliemae.com/>
      Expand Post
  • t529b (t529b)

    I was all set to tell you that this couldn't possibly work, because you're telling AD to only allow the account to log on from a specific named workstation, but when you log into Okta from your browser, you're not logging into AD from your local machine, so the attempt is doomed to fail. And then I had a light bulb moment...

     

    Add the name of your Okta AD Agent server to that account's logon restrictions. Assuming you're using delegated authentication, when you log into Okta, it is the AD agent server that talks to Active Directory to perform the authentication. Adding that name to the list won't allow the account to actually log into that server interactively, but it tells AD that it's OK to authenticate the user through that server.

     

    I just tested this theory in our preview environment and it seems to pan out. First I restricted a test account from logging in from anywhere except my local machine, and as you also observed, the Okta login attempt failed with a "NOT_SPECIFIED" error in the system log. Next, I added the name of our AD agent server to the account's restrictions, and then I was able to log in successfully.

     

    Going back to your original question, as Adam stated, I don't believe an account can be imported into Okta unless its parent OU is included in the import configuration settings.

     

    Expand Post
This question is closed.
Loading
For service account in OU excluded from import to Okta, how can I add that okta account and assign an APP?