<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
0D51Y00008W4KXLSA3Okta Classic EngineOkta Integration NetworkAnswered2024-05-16T20:05:12.000Z2020-05-21T10:04:26.000Z2020-05-28T04:30:14.000Z

v2o4p (v2o4p) asked a question.

Okta LDAP Agent Configuration

Hi All,

 

I downloaded the Okta LDAP Agent onto windows server 2016 and begin to configure all the necessary input on the LDAP configuration as I click next it appears an error msg " Failed to connect to the specified LDAP server"

 

Anyone have encountered this issues?

 

Thank you

 


  • sandeepk.84743 (Wipro Technologies)

    Hi Orion,

     

    What is the LDAP error code you are getting ? Is there any proxy server between LDAP server & OKTA agent ? Can you confirm if the ports are opened ? are you using LDAP administrative account to connect ? Can you share screenshot of the configuration & Error ?

    Expand Post
  • v2o4p (v2o4p)

    Hi Sandeep Khurana,

     

    What is the LDAP error code you are getting ?

    • No error code

     

    Is there any proxy server between LDAP server & OKTA agent ?

    • No Proxy server

     

    Can you confirm if the ports are opened ? are you using LDAP administrative account to connect ?

    • LDAP is configured on my AWS Managed Microsoft AD and the LDAP Ports is opened
    • Yes using administrative account to connect

     

    Can you share screenshot of the configuration & Error ?

    • Please refer to OktaLDAPerror and the configuration img

     

    Thank you

     

    Expand Post
    • Unknown file type
      The file is no longer available.
  • v2o4p (v2o4p)

    Here is the configuration img

    • Unknown file type
      The file is no longer available.
  • sandeepk.84743 (Wipro Technologies)

    Bind DN should start with cn=<userid> or uid=<somename>, DC=test,DC=com

     

    Please correct that.

  • v2o4p (v2o4p)

    Hi Sandeep Khurana,

     

    Can i check with you "ldap.mycompany.com:389", mycompany is referring to which portion?

     

    Thank you.

  • sandeepk.84743 (Wipro Technologies)

    mycompany is referring to the IP Address of the hostname of your LDAP server. In the Bind DN you need to specify a Admin userDN of your LDAP database. I hope it helps.

  • v2o4p (v2o4p)

    Hi Sandeep Khurana,

     

    Thanks for your information and guidance.

    Managed to pass through Step1

     

    Thank you

This question is closed.
Loading
Okta LDAP Agent Configuration