<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
0D50Z00008G7UdLSAVOkta Classic EngineAdministrationAnswered2024-04-30T09:18:25.000Z2016-03-24T19:48:20.000Z2017-06-29T16:39:43.000Z
  • j5v7c (j5v7c)

    You would determine that when installing the Okta AD Agent on the remote domain controller(s).
  • The Okta AD agent isn't installed on domain controllers, per Okta recommendation.  They are installed on seperate VMs.  I went through my screen shots of the install, and didn't see where I gave the agent a DC name, just the name of the domain.   Anyone else have any thoughts?  I tried turning verbose logging on the AD Agent but didn't see the info I was looking for.
  • j5v7c (j5v7c)

    They find the nearest DC using DC locator process.
  • Viswa (Customer)

    The host server on which the Okta AD agent is installed, must be a member of the same Windows domain of which your Active Directory users are members. During installation the setup will detect the Domain name and Integrated with that AD. Duriing Del Auth the same AD Domain is used for authenticating users.
  • j5v7c (j5v7c)

    I dont believe there is a log that directly tells you that.  If you are looking for a specific case for a user, you would probably have to take your okta ad agent log, find the entry for that time and user and then compare with your DC logs for user login, then that could tell you which they used.  Its a lot of manual work.  I dont see anywhere in an logs that tells you directly though.
  • j5v7c (j5v7c)

    What is the behavior after your manually stop the Okta agent on a the server for a DR test?  When you bring the service backup does it resume bing the primary?  If not, how do we 'switch back' the server we want to be the primary?  We confirmed the IWA agent does have the correct primary.
This question is closed.
Loading
Domain controllers and Okta AD Authentication