#1
  1. No Profile Picture
    Registered User
    Devshed Newbie (0 - 499 posts)

    Join Date
    Jan 2009
    Posts
    2
    Rep Power
    0

    [ERROR 32] No such object


    Hi All,

    I am new to OpenLDAP. When i have uploaded an ldif file, the entry was added successfully. but when i am trying to create a new profile through Softerra LDAP Browser, I get the following exception:

    Successfully connected to localhost
    [ERROR 32] No such object

    Contents of my sldap.conf file are as follows:
    ==============================================
    #
    # See slapd.conf(5) for details on configuration options.
    # This file should NOT be world readable.
    #
    ucdata-path ./ucdata
    include ./schema/core.schema
    include ./schema/cosine.schema
    include ./schema/inetorgperson.schema
    include ./schema/openldap.schema

    # Define global ACLs to disable default read access.

    # Do not enable referrals until AFTER you have a working directory
    # service AND an understanding of referrals.
    #referral ldap:/root.openldap.org

    pidfile ./run/slapd.pid
    argsfile ./run/slapd.args

    # Load dynamic backend modules:
    # modulepath ./libexec/openldap
    # moduleload back_bdb.la
    # moduleload back_ldap.la
    # moduleload back_ldbm.la
    # moduleload back_passwd.la
    # moduleload back_shell.la

    # Sample security restrictions
    # Require integrity protection (prevent hijacking)
    # Require 112-bit (3DES or better) encryption for updates
    # Require 63-bit encryption for simple bind
    # security ssf=1 update_ssf=112 simple_bind=64

    # Sample access control policy:
    # Root DSE: allow anyone to read it
    # Subschema (sub)entry DSE: allow anyone to read it
    # Other DSEs:
    # Allow self write access
    # Allow authenticated users read access
    # Allow anonymous users to authenticate
    # Directives needed to implement policy:
    # access to dn.base="" by * read
    # access to dn.base="cn=Subschema" by * read
    # access to *
    # by self write
    # by users read
    # by anonymous auth
    #
    # if no access controls are present, the default policy
    # allows anyone and everyone to read anything but restricts
    # updates to rootdn. (e.g., "access to * by * read")
    #
    # rootdn can always read and write EVERYTHING!

    #######################################################################
    # BDB database definitions
    #######################################################################

    database bdb
    suffix "dc=de,dc=carnot,dc=ag,dc=test"
    rootdn "cn=Manager,ou=People,dc=de,dc=carnot,dc=ag,dc=test"
    # Cleartext passwords, especially for the rootdn, should
    # be avoid. See slappasswd(8) and slapd.conf(5) for details.
    # Use of strong authentication encouraged.
    rootpw carldap
    # The database directory MUST exist prior to running slapd AND
    # should only be accessible by the slapd and slap tools.
    # Mode 700 recommended.
    directory ./data
    # Indices to maintain
    index objectClass eq


    ==============================================
    Contents of my ldif file which am uploading are as follows:
    ==============================================

    dn: ou=People,dc=de,dc=carnot,dc=ag,dc=test
    objectclass: top
    objectclass: organizationalUnit
    ou: People
    dn: uid=weblogic,ou=People,dc=de,dc=carnot,dc=ag,dc=test
    objectClass: top
    objectclass: uidObject
    objectclass: person
    sn: Weblogic
    cn: Weblogic System Account
    uid: weblogic
    userpassword: weblogic
    dn: ou=Groups,dc=de,dc=carnot,dc=ag,dc=test
    objectclass: top
    objectclass: organizationalUnit
    ou: Groups
    dn: cn=Administrators,ou=Groups,dc=de,dc=carnot,dc=ag,dc=test
    objectClass: groupOfUniqueNames
    objectClass: top
    cn: Administrators
    description: Administrators group for weblogic
    uniquemember: uid=weblogic,ou=People,dc=de,dc=carnot,dc=ag,dc=test
    dn: uid=motu,ou=People,dc=de,dc=carnot,dc=ag,dc=test
    objectClass: top
    objectclass: uidObject
    objectclass: person
    sn: motu
    cn: CARNOT System Account
    uid: motu
    userpassword: motu
    dn: uid=wltest,ou=People,dc=de,dc=carnot,dc=ag,dc=test
    objectClass: top
    objectclass: uidObject
    objectclass: person
    sn: wltest
    cn: Weblogic Test Account
    uid: wltest
    userpassword: weblogic
    dn: cn=CarnotAdmin,ou=Groups,dc=de,dc=carnot,dc=ag,dc=test
    objectClass: groupOfUniqueNames
    objectClass: top
    cn: CarnotAdmin
    description: Group for access to portals
    uniquemember: uid=motu,ou=People,dc=de,dc=carnot,dc=ag,dc=test
    uniquemember: uid=wltest,ou=People,dc=de,dc=carnot,dc=ag,dc=test
    dn: cn=Administrator,ou=Groups,dc=de,dc=carnot,dc=ag,dc=test
    objectClass: groupOfUniqueNames
    objectClass: top
    cn: Administrator
    description: Group CARNOT admins
    uniquemember: uid=motu,ou=People,dc=de,dc=carnot,dc=ag,dc=test
    uniquemember: uid=wltest,ou=People,dc=de,dc=carnot,dc=ag,dc=test


    ==============================================
    Configuration i am entering to connect to server through browser as as follows:
    ==============================================
    Base : dc=de,dc=carnot,dc=ag,dc=test
    User Dn: cn=Manager,ou=People,dc=de,dc=carnot,dc=ag,dc=test
    Password : carldap



    Can Anyone please help. I am unable understand what is the problem ?


    Thanks in advance.

    Regards,
    Manik
  2. #2
  3. No Profile Picture
    Contributing User
    Devshed Newbie (0 - 499 posts)

    Join Date
    Jan 2009
    Location
    Charlotte, NC
    Posts
    111
    Rep Power
    9
    In our slapd.conf file change
    cn=Manager,ou=People,dc=de,dc=carnot,dc=ag,dc=test
    to
    cn=Manager,dc=de,dc=carnot,dc=ag,dc=test
    the cn=manager account is always created at the BASE suffix of the Directory.
    then update your LDAP Browser config to use
    cn=Manager,dc=de,dc=carnot,dc=ag,dc=test
    and it should work
  4. #3
  5. No Profile Picture
    Registered User
    Devshed Newbie (0 - 499 posts)

    Join Date
    Jan 2009
    Posts
    2
    Rep Power
    0
    Hi,

    I have made changes as per you suggestions, but still i am facing the same problem. When i upload the ldif file, it give message entry added successfully, but unable to browse through the ldap browser.

    Unable to track where the problem is..

    Thank you..
  6. #4
  7. No Profile Picture
    Contributing User
    Devshed Newbie (0 - 499 posts)

    Join Date
    Jan 2009
    Location
    Charlotte, NC
    Posts
    111
    Rep Power
    9
    I need to ask some clarification questions at this point.
    When you use the Softerra LDAP Browser to view OpenLDAP at BASE="dc=de,dc=carnot,dc=ag,dc=test" do you see any data other than what you imported?
    Above you listed the LDIF file you say has been successfully imported to OpenLDAP. Does it contain blank lines between the entries?

    An LDIF file should have a single blank line between each new dn: entry and two or more blank lines at the end of the file. The single blank line tells the Directory that the entry has ended. The two or more blank lines at the end of the file indicates EOF. If you leave the blank lines off at the end of the file it will usually miss the last attribute of the last entry. Usually when you do not include the single blank lines between entries the Directory treats it as a single entry. if that were the case I would expect you to get an objectclass violation on the import, but you have not reported any.
    =========================SOF
    dn: ou=People,dc=de,dc=carnot,dc=ag,dc=test
    objectclass: top
    objectclass: organizationalUnit
    ou: People

    dn: uid=weblogic,ou=People,dc=de,dc=carnot,dc=ag,dc=test
    objectClass: top
    objectclass: uidObject
    objectclass: person
    sn: Weblogic
    cn: Weblogic System Account
    uid: weblogic
    userpassword: weblogic


    ====================== EOF

IMN logo majestic logo threadwatch logo seochat tools logo