1 Reply Latest reply on Jan 22, 2013 12:47 PM by Turloch O'Tierney-Oracle

    Behavior of ldap.ora in SQLDeveloper

      We currently moved over our OID Oracle Name Server to a standard Oracle DSEE LDAP instance for consolidation purposes.

      With this move, there are issues with how SQLDeveloper configured to use LDAP connectivity behaves...

      A search is done to the root of the LDAP instance looking for all "objectclass=orclContect" like so:

      Logs show: SRCH base="" scope=2 filter="(objectClass=orclContext)" attrs="cn dn"

      From my research, you can't run a rootdse search and sub to it's suffixes... at least without some hacking.

      Now on the SQLDeveloper side, we have the correct DN for where these searches should be happening listed under "DEFAULT_ADMIN_CONTEXT"

      Should we be seeing a search under the base defined under "DEFAULT_ADMIN_CONTEXT"?

      From the documentation located here I'd think so: http://docs.oracle.com/cd/B28359_01/network.111/b28317/ldap.htm

      "Use the DEFAULT_ADMIN_CONTEXT parameter to specify the default directory entry that contains an Oracle Context from which connect identifiers can be created, modified, or looked up."

      Any ideas folks?
        • 1. Re: Behavior of ldap.ora in SQLDeveloper
          Turloch O'Tierney-Oracle
          Hi rdwalker,

          Currently in SQLDeveloper we only support OID. Feature Request is
          "Retrieve Oracle connection from a LDAP other than the Oracle OID."
          If you want to vote on it (also name the LDAP software being used).
          SQL*Net allows LDAP connections via custom url which can be entered via SQLDeveloper connection type: Advanced -> Custom JDBC URL

          -SQLDeveloper Team