-
Notifications
You must be signed in to change notification settings - Fork 0
/
UPGRADE
49 lines (32 loc) · 1.65 KB
/
UPGRADE
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
UPGRADING FROM 0.9.2 OR BEFORE TO 0.9.4 or later
------------------------------------------------
Due to a schema change that appeared in versions 0.9.3 and 0.9.4,
you'll need to update your existing LDAP data. Unfortunately, there
is no easy way to do this. Many attributes that were in MAY have
become MUST items, some attributes have been removed, and some entries
are in an entirely new objectClass. Basically, things that Jamm
depends on being there have now been moved into MUST.
The following are the steps I followed to update my LDAP server:
1) Dump the current database to an LDIF. It's important to do this as
manager so that all attributes get saved.
ldapsearch -b "o=hosting,dc=kgarner,dc=com" \
-D "cn=Manager,o=hosting,dc=kgarner,dc=com" -W -x > dump.ldif
2) Edit the dump.ldif file.
To update your data, do the following:
o For each JammVirtualDomain entry: remove editCatchAlls and
editAliases, and add delete, and make sure lastChange has a
value.
o For each JammMailAccount entry: add delete and make sure
lastChange has a value.
o The JammMailAlias entries should be okay.
Also included in the distribution is a Perl script named
updateLdif.pl. It'll take your current LDIF and produce a new LDIF
file that is up to date with the new fields as per above. It
requires the Net::LDAP and Set::Scalar Perl modules.
./updateLdif.pl dump.ldif fixed-dump.ldif
3) Shut down slapd.
4) Backup and remove your original database files.
5) Copy new schema file into place for the LDAP server.
6) Restart slapd.
7) Load the cleaned up data into LDAP.
ldapadd -D "cn=Manager,o=hosting,dc=kgarner,dc=com" -W -x -f fixed-dump.ldif