Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
# 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!
database bdb
suffix "dc=test,dc=com"
rootdn "cn=Manager,dc=test,dc=com"
# Cleartext passwords, especially for the rootdn, should
# be avoided. See slappasswd(8) and slapd.conf(5) for details.
# Use of strong authentication encouraged.
rootpw Redhat
# rootpw {crypt}ijFYNcSNctBYg
# The database directory MUST exist prior to running slapd AND
# should only be accessible by the slapd and slap tools.
# Mode 700 recommended.
directory /var/lib/ldap
# Indices to maintain for this database
index objectClass eq,pres
index ou,cn,mail,surname,givenname eq,pres,sub
index uidNumber,gidNumber,loginShell eq,pres
index uid,memberUid eq,pres,sub
index nisMapName,nisMapEntry eq,pres,sub
So could you please explain me why i am getting this error.
Thanks in advance.
Last edited by Rohit_4739; 09-08-2011 at 05:04 AM.
It should work as the bind dn and password are those defined in slapd.conf. Are you sure you're using that slapd.conf and not a different one?
Also since you didn't mention your distro, check if you're not running openldap with the configuration stored in cn=config instead of slapd.conf.
#useradd test
#passwd test
Changing password for user test1.
New UNIX password:
Retype new UNIX password:
passwd: all authentication tokens updated successfully.
The users created here are the users of operating system. Now migrate them to Openldap.
Before doing this create root user with the name "root"
Now migrate:
#/usr/share/openldap/migration/migrate_passwd.pl /etc/openldap/passwd.root /etc/openldap/root.ldif (This is for root migration)
#/usr/share/openldap/migration/migrate_passwd.pl /etc/openldap/passwd.test /etc/openldap/test.ldif
After adding the root user add contents of the root as per the requirement
We have to follow clear structure before we add users to openldap.
First we need to Create Organisation (Organisation)
Second we need to create Organisation structure (Bussiness Unit)
Thirdly we have to add inetorgperson (Group/member)
i.e follow the below structure.
By following above structure you can overcome the error.
Again, as in a couple of other threads that you've re-opened, this is not correct. It will ONLY work for someone who wants the same configuration as you. And this thread has been closed for over a year now....please don't reopen old threads for no reason.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.