<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
0D54z00009Ogw4jCABOkta Classic EngineAuthenticationAnswered2023-06-28T19:01:08.000Z2023-06-27T19:40:39.000Z2023-06-28T19:01:08.000Z
New AD accounts are imported but cannot authenticate through delegated authority.

Current / Previous AD accounts are working for authentication, New AD accounts are not. Accounts are in the same OU. Even attempting a temp password, the process times out. Reinstalled the agent with no success.


  • Hi Mihai, thank you for responding. The issue ended up being AD replication. Recent AD work, the Domain Controller sitting in the DMZ, was removed. No add or cleanup was done in Sites and Services. There was not a secondary DC that OKTA could find. New accounts weren't getting replicated. We figured it out late last night. Thanks again.

    Selected as Best
  • Hi @User16802694712542789369 (Customer)​ , Thank you for reaching out to the Okta Community!

     

    From the Okta side of things, Delegated Authentication either works or it does not. It would not impact a subset of users, so my focus would be the specific accounts. 

    I would start by checking the System Logs for the failed login attempts in case those specific users hit some kind of sign-on policy that denies access. 

    If that's not the case, I would check the AD logs for explicit error messages (error codes). 

    Most common that I've seen in my experience were: 

     

    ERROR_LOGON_FAILURE

    1326 (0x52E)

    The user name or password is incorrect.

     

    ERROR_INVALID_WORKSTATION

    1329 (0x531)

    This user isn't allowed to sign in to this computer.

     

    ERROR_PASSWORD_EXPIRED

    1330 (0x532)

    The password for this account has expired.

     

    ERROR_ACCOUNT_DISABLED

    1331 (0x533)

    This user can't sign in because this account is currently disabled.

     

     

     

     

    If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you. 

     

    Hope my answer helps! 

    --------------------------------

    Community members help others by clicking Like or Select as Best on responses. Try it today.

    Expand Post
  • Hi Mihai, thank you for responding. The issue ended up being AD replication. Recent AD work, the Domain Controller sitting in the DMZ, was removed. No add or cleanup was done in Sites and Services. There was not a secondary DC that OKTA could find. New accounts weren't getting replicated. We figured it out late last night. Thanks again.

    Selected as Best
    • Had a feeling it was something environmental, but to be honest Replication hadn't crossed my mind. Good to know.

      Thanks for sharing. I'm sure it will come in handy for anyone else experiencing something similar.

  • We knew the Domain Controller was changed out but we didn't have any other issues; logging in, self service PW reset. All current users were fine, just new accounts. And the new accounts could log in. I wasn't in on the DC swap so had to start from scratch. Took us almost a week to figure out.

This question is closed.
Loading
New AD accounts are imported but cannot authenticate through delegated authority.