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.
# This file should NOT be world readable.
#
include /etc/openldap/schema/core.schema
include /etc/openldap/schema/cosine.schema
include /etc/openldap/schema/inetorgperson.schema
include /etc/openldap/schema/nis.schema
# Allow LDAPv2 client connections. This is NOT the default.
allow bind_v2
# Do not enable referrals until AFTER you have a working directory
# service AND an understanding of referrals.
#referral ldap://root.openldap.org
database bdb
suffix "dc=www,dc=ycsmumldap,dc=com"
rootdn "cn=Manager,dc=www,dc=ycsmumldap,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 {SSHA}7OcFiJgR39BbA7Oj+K4nGEbr33VkNYRH
# 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/ycsmumldap.com
# 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
# Replicas of this database
#replogfile /var/lib/ldap/openldap-master-replog
My ldapsearch result is as follows
[root@www ycsmumldap.com]# ldapsearch -x -b '' -s base '(objectclass=*)' namingContexts
# extended LDIF
#
# LDAPv3
# base <> with scope baseObject
# filter: (objectclass=*)
# requesting: namingContexts
#
[root@www ycsmumldap.com]# ldapadd -f /ldapusers/user.ldif -x -D "cn=Manager,dc=www,dc=ycsmumldap,dc=com" -w link@123
adding new entry "dc=www,dc=ycsmumldap,dc=com"
ldapadd: Naming violation (64)
additional info: value of naming attribute 'dc' is not present in entry
My ldapsearch result is as follows
[root@www ycsmumldap.com]# ldapsearch -x -b '' -s base '(objectclass=*)' namingContexts
# extended LDIF
#
# LDAPv3
# base <> with scope baseObject
# filter: (objectclass=*)
# requesting: namingContexts
#
Next ldapadd gave error.The error is as follows
[root@www ycsmumldap.com]# ldapadd -f /ldapusers/user.ldif -x -D "cn=Manager,dc=www,dc=ycsmumldap,dc=com" -w link@123
adding new entry "dc=www,dc=ycsmumldap,dc=com"
ldapadd: Naming violation (64) additional info: value of naming attribute 'dc' is not present in entry
My user.ldif file configuration is
dn: dc=www,dc=ycsmumldap,dc=com
dc: ycsmumldap
objectClass: dcObject
objectClass: organizationalUnit
o: ycsmumldap
now I have another doubt ....clarify me......how to set passwd users who added into ldap database.......how to login with that username in client systems.......
Thank you very much,
your post was very helpful for me....
now I have another doubt ....clarify me......how to set passwd users who added into ldap database.......how to login with that username in client systems.......
The words "doubt" and "question" mean different things.
And "client systems" is too vague. What KIND of client? Windows? Mac? Linux? Solaris? What???? Each one will have different ways to connect to and use LDAP. Google can point you to them.
su - yal2361
Password:
su: warning: cannot change directory to /home/yal2361: No such file or directory
-bash-3.2$
The error gives whenever i try to login in client machine.
should i need to create home directory for that user in client machine........Is there any way to solve this......please suggest me...
Thank you very mauch
I did "suggest you". Check the permissions on the specified home directory. Obviously if it doesn't exist, it needs to be created.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.