summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorThomas Arendsen Hein <thomas@intevation.de>2011-04-15 14:13:55 (GMT)
committerChristoph Wickert <wickert@kolabsys.com>2011-04-15 20:03:15 (GMT)
commit2abfe208b4f45410a42393dd0c207e2a9c4a844b (patch)
treed14b0edd1d47cad3809a6683a7055afa33826efc
parentc82714e97ea557b6af17c1fe65a9520366fd3ce9 (diff)
downloadserver-2abfe208b4f45410a42393dd0c207e2a9c4a844b.tar.gz
1st.README: 2.3.0 still uses cn instead of uid for dn, remove upgrade docs
kolab/issue1549 (Patch to change dn: cn=... -> dn: mail=...) and release-notes do not mention that this was included and the code still uses cn.
-rw-r--r--1st.README32
1 files changed, 3 insertions, 29 deletions
diff --git a/1st.README b/1st.README
index 69cabee..182f01f 100644
--- a/1st.README
+++ b/1st.README
@@ -203,43 +203,17 @@ otherwise your setup might seem to work fine, but will not work reliably!
file that contains "SYNTAX 1.3.6.1.4.1.1466.115.121.1.11" or use the
backup of both files you created in step 0.
-8. In previous versions of the Kolab Server, the Distinguished Name (dn)
- of users was built from their common name (cn) attribute and the cn
- was built from the attributes 'givenName' (e.g. John) and 'sn' (Doe).
- Therefore it was not possible to have two users of the same name or
- two accounts for the same person (cn=John Doe) since each dn must be
- distinct.
-
- Kolab 2.3 uses the 'uid' attribute to build the dn. This change is
- backwards compatible. Existing users will continue to use the old dn
- while new users will be created following the new scheme. This means
- that you can create an account with the same cn after the upgrade.
-
- To take however full advantage of the new scheme, you need to convert
- your LDAP with the script 'kolab-cn2uid' which you can download from
- http://kolab.org/cgi-bin/viewcvs-kolab.cgi/*checkout*/utils/admin/kolab-cn2uid
- (https:// can be used to provide a secure download, if you import
- the corresponding root certificate from https://ssl.intevation.de/)
-
- If you want to convert your existing LDAP, please run the following
- commands as root:
-
- # mv ~/kolab-update.ldif ~/kolab-dn-cn.ldif || \
- cp ~/kolab-2.2.4.ldif ~/kolab-dn-cn.ldif
- # (umask 077 && /kolab/bin/php \
- kolab-cn2uid -i ~/kolab-dn-cn.ldif -o ~/kolab-update.ldif)
-
-9. Before starting the LDAP server the database must be restored from
+8. Before starting the LDAP server the database must be restored from
the ldif:
# rm /kolab/var/openldap/openldap-data/*
# /kolab/sbin/slapadd -l ~/kolab-update.ldif
-10. Manually transfer local changes of templates from .rpmsave into the
+9. Manually transfer local changes of templates from .rpmsave into the
new templates and remove all .rpmsave files below /kolab/etc as
discussed in the "General update instructions" above.
-11. Start the OpenLDAP, generate the configuration files and start the
+10. Start the OpenLDAP, generate the configuration files and start the
Kolab server:
# /kolab/bin/openpkg rc openldap start