Re: An unknown error has occured!

Keith,

I'm still not able to get it connected.  I've never setup openldap, so 
I'm not sure exactly how you're supposed to test it, however I wrote a 
simple perl script (its at the bottom) that is able to bind to ldap and 
port scans are showing the port open.  That doesn't cover any issues 
with Tomcat or Java, but as far as I can tell ldap is running, and it 
can be connected to.

Levi

Here is my java version:

java version "1.4.2_08"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_08-b03)
Java HotSpot(TM) Client VM (build 1.4.2_08-b03, mixed mode)


"allow bind_v2" is in my config, I tried changing it to "allow bindv2", 
but then ldap wouldn't start.  Here is my slapd.conf:

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

password-hash {CRYPT}

# 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!

access to dn=".*,jvd=([^,]+),o=hosting,dc=cuemedia,dc=com"
        attr=userPassword
    by self write
    by 
group/jammPostmaster/roleOccupant="cn=postmaster,jvd=$1,o=hosting,dc=cuem
edia,dc=com"  write
    by dn="cn=dovecot,dc=cuemedia,dc=com" read
    by anonymous auth
    by * none

access to dn=".*,jvd=([^,]+),o=hosting,dc=cuemedia,dc=com"
    by self write
    by 
group/jammPostmaster/roleOccupant="cn=postmaster,jvd=$1,o=hosting,dc=cuem
edia,dc=com" write
    by * read

access to *
   by * read

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

database        ldbm
suffix          "dc=cuemedia,dc=com"
rootdn          "cn=Manager,dc=cuemedia,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                secret
# rootpw                {crypt}ijFYNcSNctBYg
rootpw {SSHA}XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXx

# 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

# 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/[email protected]
loglevel -1



Here is my perl script:

#!/usr/bin/perl
use Net::LDAP;

$ldap = Net::LDAP->new("127.0.0.1");
$mesg = $ldap->bind("cn=Manager,dc=cuemedia,dc=com", password=>"XXXXX");

print $mesg."\n";
$ldap->unbind;


exit 0;

Keith T. Garner wrote:

>On Mon, Jun 13, 2005 at 03:46:05, Levi Senft said:
>  
>
>>I have the firewall (Fedora Core 2) turned off.  ldap and jamm are 
>>running on the same machine.  If I do a portscan the ldap port is open 
>>(389) on the loop back and ethernet  interfaces.  I also installed 
>>"phpLDAPadmin" and it is able to connect to LDAP and I can login and 
>>browse the entries created for jamm.
>>    
>>
>
>What is the output of "java -version"?
>
>Do you have "allow bindv2" in your slapd.conf?
>
>Keith
>
>  
>


-- 
Levi Senft
Cue Media
Web Developer

Tel: (801) 961-9216
Web: http://www.cuemedia.com
Email: [email protected]



-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click