Issue 804 - Difficult Migration openldap 1.X->2.X
Summary: Difficult Migration openldap 1.X->2.X
Status: VERIFIED FIXED
Alias: None
Product: OpenLDAP
Classification: Unclassified
Component: slapd (show other issues)
Version: unspecified
Hardware: All All
: --- normal
Target Milestone: ---
Assignee: OpenLDAP project
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2000-10-04 16:41 UTC by frederic.bernoud@altiva.fr
Modified: 2014-08-01 21:06 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description frederic.bernoud@altiva.fr 2000-10-04 16:41:13 UTC
Full_Name: Fr�d�ric BERNOUD
Version: 2.04
OS: mdk7.1
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (213.19.2.88)


I'd like update to openldap 2.X, but I've a problem to use the 
new system class of 2.X. I think the shema of 2.04 are incomplete 
to compare with 1.X. because I can't add mail information in the new version.
 

Before 2.X I had this struture :

#Base
dn :dc=altiva,dc=fr
o :altiva					
objectClass :organization

#Structure
dn :ou=People,dc=altiva,dc=fr
objectClass :organizationalUnit
ou :People

dn :ou=Group,dc=altiva,dc=fr
objectClass :organizationalUnit
ou :Group


#exemple of data for People
dn: uid=fred,ou=People,dc=altiva,dc=fr
uid: fred
cn: Frederic BERNOUD

#mail information work with 1.X but not in 2.X
mail:herve@altiva.fr


objectClass: account
objectClass: posixAccount
objectClass: top
objectClass: shadowAccount
userPassword: {crypt}!$1$284eIpsm$edOVxfaf4yIQz1rDGr6l..
shadowLastChange: 11089
shadowMin: -1
shadowMax: -1
shadowWarning: -1
shadowInactive: -1
shadowExpire: -1
shadowFlag: 134531808			
loginShell: /bin/sh
uidNumber: 502
gidNumber: 100
homeDirectory: /home/fred
gecos: fred


#exemple of data for Group
dn: cn=users,ou=Group,dc=altiva,dc=fr
objectClass: posixGroup
objectClass: top
cn: users
userPassword: {crypt}x
gidNumber: 100
memberUid: fred

It workes fine, but with the new version openldap 2.04 
I must remove "mail:herve@altiva.fr".

It seem the class is incomplete??

My slapd.conf (2.04) :
------------------------------------------------------------------------------------------------
# $OpenLDAP: pkg/ldap/servers/slapd/slapd.conf,v 1.8.8.4 2000/08/26 17:06:18
kurt Exp $
#
# See slapd.conf(5) for details on configuration options.
# This file should NOT be world readable.
#

# ;permet d'inclure un fichier, dans ce cas, les definitions des objets
#include		/etc/openldap/slapd.at.conf
#include		/etc/openldap/slapd.oc.conf

include		/etc/openldap/schema/core.schema
include		/etc/openldap/schema/cosine.schema
#include		/etc/openldap/schema/corba.schema
include		/etc/openldap/schema/inetorgperson.schema
#include		/etc/openldap/schema/java.schema
#include		/etc/openldap/schema/krb5-kdc.schema
##include		/etc/openldap/schema/list
#include		/etc/openldap/schema/microsoft.ext.schema
#include		/etc/openldap/schema/microsoft.schema
#include		/etc/openldap/schema/microsoft.std.schema
#include		/etc/openldap/schema/misc.schema
#include		/etc/openldap/schema/nadf.schema
#include		/etc/openldap/schema/nis.schema
#include		/etc/openldap/schema/openldap.schema
#include		/etc/openldap/schema/pilot.schema

#include		/etc/openldap/schema/openldap.schema

# Define global ACLs to disable default read access.

# 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_ldap.la
# moduleload	back_ldbm.la
# moduleload	back_passwd.la
# moduleload	back_shell.la

#######################################################################
# ldbm database definitions
#######################################################################

database	ldbm

suffix		"dc=altiva, dc=fr"
rootdn		"cn=root, dc=altiva, dc=fr"

# Cleartext passwords, especially for the rootdn, should
# be avoid.  See slappasswd(8) and slapd.conf(5) for details.
# Use of strong authentication encouraged.
rootpw		secret

# The database directory MUST exist prior to running slapd AND 
# should only be accessable by the slapd/tools. Mode 700 recommended.
directory	/usr/var/openldap-ldbm


# Indices to maintain		
index	objectClass	eq




My old slapd.conf which is ok with openldap 1.X

# $OpenLDAP: pkg/ldap/servers/slapd/slapd.conf,v 1.8.8.4 2000/08/26 17:06:18
kurt Exp $
#
# See slapd.conf(5) for details on configuration options.
# This file should NOT be world readable.
#

# ;permet d'inclure un fichier, dans ce cas, les definitions des objets
include		/etc/openldap/slapd.at.conf
include		/etc/openldap/slapd.oc.conf

include		/etc/openldap/schema/core.schema

# Define global ACLs to disable default read access.

# 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_ldap.la
# moduleload	back_ldbm.la
# moduleload	back_passwd.la
# moduleload	back_shell.la

#######################################################################
# ldbm database definitions
#######################################################################

database	ldbm

suffix		"dc=altiva, dc=fr"
rootdn		"cn=root, dc=altiva, dc=fr"

# Cleartext passwords, especially for the rootdn, should
# be avoid.  See slappasswd(8) and slapd.conf(5) for details.
# Use of strong authentication encouraged.
rootpw		secret

# The database directory MUST exist prior to running slapd AND 
# should only be accessable by the slapd/tools. Mode 700 recommended.
directory	/usr/var/openldap-ldbm


# Indices to maintain
index	objectClass	eq

Comment 1 Julio Sanchez 2000-10-04 17:32:00 UTC

frederic.bernoud@altiva.fr wrote:

> 
> I'd like update to openldap 2.X, but I've a problem to use the
> new system class of 2.X. I think the shema of 2.04 are incomplete
> to compare with 1.X. because I can't add mail information in the new version.
 
> #exemple of data for People
> dn: uid=fred,ou=People,dc=altiva,dc=fr
> uid: fred
> cn: Frederic BERNOUD
> 
> #mail information work with 1.X but not in 2.X
> mail:herve@altiva.fr
> 
> objectClass: account
> objectClass: posixAccount
> objectClass: top
> objectClass: shadowAccount

If I remember correctly, none of those classes allows the mail attribute
type.  So that entry always was a schema violation.  Formerly, schema
checks defaulted to 'off', they now default to 'on'.  I do not
recommend that you relax the schema checks but fix your data instead.

Julio
Comment 2 Kurt Zeilenga 2000-10-05 08:51:50 UTC
changed notes
changed state Open to Closed
Comment 3 OpenLDAP project 2014-08-01 21:06:12 UTC
invalid input