Commit 62351326 authored by bmortier's avatar bmortier

Merge branch '5805-contrib-doc-readme-ldap-migration-should-be-merged-to-readme-md' into '1.3-dev'

Resolve "contrib/doc/README.ldap-migration should be merged to README.md"

Closes #5805

See merge request fusiondirectory/fd!185
parents 99b8ed52 24cb02ec
......@@ -41,7 +41,24 @@ This question can be solved by creating:
## Installation and upgrade of FusionDirectory
The installation and upgrade information is available on [fusiondirectory-install]
The installation and upgrade information is available on [Install FusionDirectory][fusiondirectory-install]
## Migration to FusionDirectory
To migrate an existing LDAP tree, you've to do all steps [Install FusionDirectory][fusiondirectory-install],
plus some modifications:
* FusionDirectory only shows users that have the objectClass inetOrgPerson
* FusionDirectory only recognizes subtrees (or departments in FusionDirectory's view of things) that have the objectClass gosaDepartment.
You can hide subtrees from FusionDirectory by not putting this objectClass inside.
The FusionDirectory setup may be used to do these migrations, but it is not meant
to work in every possible circumstance. Please be carefull when using it on
productive system.
That should be all. Entries should be visible in FusionDirectory now.
Be aware that if your naming policy of user cn's differs from the way FusionDirectory handles it, the entries get rewritten to a FusionDirectory style dn.
## Get help
......
LDAP TREE MIGRATION
===================
To migrate an existing LDAP tree, you've to do all steps from above,
plus some modifications:
- FusionDirectory only shows users that have the objectClass inetOrgPerson
- FusionDirectory only recognizes subtrees (or departments in FusionDirectory's
view of things) that have the objectClass gosaDepartment. You can hide subtrees
from FusionDirectory by not putting this objectClass inside.
The FusionDirectory setup may be used to do these migrations, but it is not meant
to work in every possible circumstance. Please be carefull when using it on
productive system.
That should be all. Entries should be visible in FusionDirectory now. Be aware that if
your naming policy of user cn's differs from the way FusionDirectory handles it, the
entries get rewritten to a FusionDirectory style dn.
Have fun!
---
* Further information
To improve this piece of software, please report all kind of errors using the bug tracker
on https://gitlab.fusiondirectory.org/
Documentation: http://documentation.fusiondirectory.org/
Mailinglist: http://lists.fusiondirectory.org/
Irc: #fusiondirectory on freenode
---
The FusionDirectory project <contact@fusiondirectory.org>
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment