Skip to content
GitLab
Commit 4eecfc49 authored by bmortier's avatar bmortier
Browse files

Merge branch... 

Merge branch '6105-fix-reference-to-the-documentation-after-moving-around-fusiondirectory-documentationin-upgrade' into '1.4-dev'

Resolve "fix reference to the documentation after moving around fusiondirectory documentationin UPGRADE.md and README.md"

Closes #6105

See merge request fusiondirectory/fd-plugins!842
parents 08eb118b 8f89b6c3
dev 6104-mail-methods-refactor 6231-give-the-ability-to-the-webservice-to-notice-if-an-attribute-is-monovalued-or-multivalued 6237-add-requiredattrs-array-to-the-webservice-informations 6245-adapt-the-ci-to-the-reorganisation-of-the-dev-tools-and-fixing-the-trigger-downstream-pipelines 6250-supann-configuration-backend-requires-account-life-cycle-section 6280-plugins-update-plugins-to-take-into-consideration-the-new-directory-of-core-structure 6310-tasks-reminder-error-in-the-schema-duplicate-attribute-id 6311-put-the-version-1-5-in-all-yaml-for-fusiondirectory-1-5 6322-template-issue-when-creating-a-template-with-empty-password-error-message-should-not-be-seen-2 6332-zimbra-allows-update-of-data-for-unknown-domain-name-for-specific-individual-aliases 6337-webservice-issue-with-archiving-post-request-not-responding-but-successfully-archiving-user 6341-supann-extract-resources-states-sub-states-from-backend-configuration-to-their-own-objects master fusiondirectory-1.5 fusiondirectory-1.4
No related merge requests found
Hide whitespace changes
Inline Side-by-side
Showing
with 23 additions and 0 deletions
+23 -0
README.md
+ 23
− 0
View file @ 4eecfc49
...@@ -39,6 +39,27 @@ This question can be solved by creating: ...@@ -39,6 +39,27 @@ This question can be solved by creating:
* A plugin for its management in FusionDirectory with the simple plugin api * A plugin for its management in FusionDirectory with the simple plugin api
* An Argonaut module for the client installed on the server * An Argonaut module for the client installed on the server
## Installation and upgrade of FusionDirectory
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 ## Get help
### Community support ### Community support
...@@ -84,6 +105,8 @@ If you like us and want to send us a small contribution you can use the followin ...@@ -84,6 +105,8 @@ If you like us and want to send us a small contribution you can use the followin
[FusionDirectory]: https://www.fusiondirectory.org/ [FusionDirectory]: https://www.fusiondirectory.org/
[fusiondirectory-install]: https://fusiondirectory-user-manual.readthedocs.io/en/1.3/fusiondirectory/install/index.html
[get help]: https://www.fusiondirectory.org/en/communaute/ [get help]: https://www.fusiondirectory.org/en/communaute/
[get support]: https://www.fusiondirectory.org/en/support/ [get support]: https://www.fusiondirectory.org/en/support/
......
Supports Markdown
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