This is a discussion on Ldap profile within the Linux software forums, part of the Linux Getting Started category; I am fecing the problem of LDAP when i am trying to add items in Ldap database by the command ...
|
|||||||
| Register | FAQ | Members List | Calendar | Forgotten your password? | Mark Forums Read |
|
|||
|
I am fecing the problem of LDAP
when i am trying to add items in Ldap database by the command it is showing this error: ldapadd -x -D "cn=Manager,dc=linserver,dc=com" -W -f /etc/openldap/root.ldif Enter passowrd: ldap_bind: Invalid Credential (49) This error is comming when i am trying with password as "control" This is my slapd.conf file # # See slapd.conf(5) for details on configuration options. # 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 #include /etc/openldap/schema/redhat/autofs.schema include /etc/openldap/schema/dnszone.schema include /etc/openldap/schema/misc.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 pidfile /var/run/slapd.pid argsfile /var/run/slapd.args # Load dynamic backend modules: modulepath /usr/sbin/openldap moduleload back_bdb.la moduleload back_ldap.la moduleload back_ldbm.la moduleload back_passwd.la moduleload back_shell.la # The next three lines allow use of TLS for encrypting connections using a # dummy test certificate which you can generate by changing to # /usr/share/ssl/certs, running "make slapd.pem", and fixing permissions on # slapd.pem so that the ldap user or group can read it. Your client software # may balk at self-signed certificates, however. # TLSCACertificateFile /usr/share/ssl/certs/ca-bundle.crt # TLSCertificateFile /usr/share/ssl/certs/slapd.pem # TLSCertificateKeyFile /usr/share/ssl/certs/slapd.pem # 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! ################################################## ##################### # ldbm and/or bdb database definitions ################################################## ##################### database ldbm suffix "dc=linserver,dc=com" rootdn "cn=Manager,dc=linserver,dc=com" # Cleartext passwords, especially for the rootdn, should # be avoided. See slappasswd( # Use of strong authentication encouraged. rootpw {CRYPT}seFfFFwZiaAls # 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/linserver.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 #replica host=ldap-1.example.com:389 starttls=critical # bindmethod=sasl saslmech=GSSAPI # authcId=host/ldap-master.example.com@EXAMPLE.COM -----------------------X--------------------X---------- This is my root.ldif file dn: uid=root,ou=People,dc=linserver,dc=com uid: root cn: root objectClass: account objectClass: posixAccount objectClass: top objectClass: shadowAccount userPassword: {crypt}$1$.FR3McU0$0/09ivtPaYM7/3PIbpVoO0 shadowLastChange: 13447 shadowMax: 99999 shadowWarning: 7 loginShell: /bin/bash uidNumber: 0 gidNumber: 0 homeDirectory: /root gecos: root dn: uid=operator,ou=People,dc=linserver,dc=com uid: operator cn: operator objectClass: account objectClass: posixAccount objectClass: top objectClass: shadowAccount userPassword: {crypt}* shadowLastChange: 13404 shadowMax: 99999 shadowWarning: 7 loginShell: /sbin/nologin uidNumber: 11 gidNumber: 0 homeDirectory: /root gecos: operator |
| Sponsored Links | ||
|
|
![]() |
| Bookmarks |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) |
|
| Thread Tools | |
| Display Modes | |
|
|
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| LDAP authentication | pansarevai | Ubuntu / Debian | 0 | 01-09-2008 04:42 PM |
| Any SSH client which can store 100's of login profile? | deltamails | Linux software | 14 | 09-24-2007 04:13 PM |
| Ldap Server Configuration | sumit | Linux hardware | 0 | 08-17-2007 10:43 PM |
| LDAP and RADIUS | mannrj45 | Linux software | 1 | 12-02-2006 09:40 PM |
| Open LDAP | vasanth | Linux software | 2 | 02-11-2005 04:49 PM |