again with the ldap questions

projkt4 · #1 8th September 2004, 07:24 AM

Hi all, by the time im done with the questions, we'll be able to search the forum and be able to answer any ldap question theat comes our way. so here we go:

i try and search or add, i get a password prompt, i enter the password, which i have left as the default of "secret" now when i enter that, i get this promt:

Code:

ldap_sasl_interactive_bind_s: Internal (implementation specific) error (80)
        additional info: SASL(-13): user not found: no secret in database

what does it mean, no secret in database? i thought that ldap didn't use the default password file; the one used for default authentication. or am i looking in the wrong direction. my linux guru told me that he was only using single user authentication, which i feel defeats the purpose of using ldap. how can i get this to work, i have yet to be able to add my admin profile. i have been working on this for a few days and i cant get past this part. searching leads me to a few examples that i have tried to duplicat and cannot seem to get working, what am i doing wrong?

bryancole · #2 8th September 2004, 08:06 AM

Can you give a few more details: What search command are you trying to execute, what's in slapd.conf etc. etc.?

bc

projkt4 · #3 8th September 2004, 08:27 AM

i started with a basic "ldapsearch" no specifications.

from the beginning:

Code:

[root@Klamathia dbased]# slapd -t
config check succeeded

so when i run:

Code:

[root@Klamathia dbased]# ldapsearch -x -b '' -s base '(objectclass=*)' namingContexts
# extended LDIF
#
# LDAPv3
# base <> with scope base
# filter: (objectclass=*)
# requesting: namingContexts
#

#
dn:
namingContexts: dc=frontier,dc=org

# search result
search: 2
result: 0 Success

# numResponses: 2
# numEntries: 1

and here's my current slapd.conf

Code:

# $OpenLDAP: pkg/ldap/servers/slapd/slapd.conf,v 1.23.2.8 2003/05/24 23:19:14 kurt Exp $
#modified by projkt4
#
# 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

# 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 connections using a dummy test
# certificate, but you should generate a proper certificate 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.
# 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 is:
#       Allow read by all
#
 rootdn can always write!

#######################################################################
# ldbm and/or bdb database definitions
#######################################################################

database        ldbm
suffix          "dc=frontier,dc=org"
rootdn          "cn=admin,dc=frontier,dc=org"
# Cleartext passwords, especially for the rootdn, should
# be avoided.  See slappasswd(8) and slapd.conf(5) for details.
# Use of strong authentication encouraged.
 rootpw         secret
# rootpw                {CRYPT}crxIGeG7XOoEU

# The database directory MUST exist prior to running slapd AND
# should only be accessible by the slapd and slap tools.
# Mode 700 recommended.
directory       /admin/dbased/openldap-data

# 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 tls=yes
#     bindmethod=sasl saslmech=GSSAPI
#     authcId=host/ldap-master.example.com@EXAMPLE.COM

projkt4 · #4 8th September 2004, 08:32 AM

one last thing

just ldapsearch:

Code:

[root@Klamathia dbased]# ldapsearch
SASL/DIGEST-MD5 authentication started
Please enter your password:
ldap_sasl_interactive_bind_s: Internal (implementation specific) error (80)
        additional info: SASL(-13): user not found: no secret in database