Rename of directory.nh for multiple migrations #7103
Labels
milestone goal 👑
This describes an announced milestone goal
verified
All test cases were verified successfully
Milestone
Comments
DavidePrincipi
added
the
milestone goal 👑
DavidePrincipi
changed the title
This was referenced Nov 18, 2024
Merged
This was referenced Nov 21, 2024
stephdl
added a commit
to NethServer/ns8-nextcloud
that referenced
this issue
Nov 22, 2024
Load LDAP domain from config and enhance Nextcloud service management NethServer/dev#7103
stephdl
added a commit
to NethServer/ns8-sogo
that referenced
this issue
Nov 22, 2024
Add LDAP configuration script for user-domain-changed event NethServer/dev#7103
stephdl
added a commit
to NethServer/ns8-roundcubemail
that referenced
this issue
Nov 22, 2024
Autodiscover user domain and set environment variable NethServer/dev#7103
stephdl
added a commit
to NethServer/ns8-mail
that referenced
this issue
Nov 25, 2024
Fix event user-domain-changed NethServer/dev#7103
gsanchietti
added a commit
to NethServer/nethserver-ns8-migration
that referenced
this issue
Nov 25, 2024
Changes: - add new env variable USER_DOMAIN - ns8-join: add dynamic baseDN for OpenLDAP - ui: add new field for entering OpenLDAP user domain NethServer/dev#7103 Co-authored-by: Giacomo Sanchietti <[email protected]> Co-authored-by: Davide Principi <[email protected]>
|
in
|
stephdl
added a commit
to NethServer/ns8-ejabberd
that referenced
this issue
Nov 25, 2024
Fix user-domain-changed event NethServer/dev#7103
stephdl
added a commit
to NethServer/ns8-nextcloud
that referenced
this issue
Nov 25, 2024
Remove deprecated LDAP script and enhance Nextcloud integration NethServer/dev#7103
stephdl
added a commit
to NethServer/ns8-webtop
that referenced
this issue
Nov 26, 2024
Register user domain change event handling NethServer/dev#7103
|
Testing release |
|
in
|
stephdl
added a commit
to NethServer/nethserver-ns8-migration
that referenced
this issue
Dec 5, 2024
ui: move ldap field on the top NethServer/dev#7103
|
in
|
stephdl
added a commit
to NethServer/nethserver-ns8-migration
that referenced
this issue
Dec 6, 2024
Include LDAP user domain in connection configuration NethServer/dev#7103
|
in
|
This comment has been minimized.
This comment has been minimized.
DavidePrincipi
added a commit
to NethServer/nethserver-ns8-migration
that referenced
this issue
Dec 6, 2024
If NS8 cannot contact the NS7 LDAP service the port_connection_error validation message is returned. This happens for example if slapd service has non-default values in TCPPorts and/or access props. Refs NethServer/dev#7103
|
in
|
|
in
|
|
TODO:
|
|
in
|
|
Release |
|
in
|
stephdl
added a commit
to NethServer/ns8-docs
that referenced
this issue
Dec 10, 2024
Document OpenLDAP account providers DN migration NethServer/dev#7103
|
Release |
|
this one too needs to be closed: #7199 |
|
in
|
|
released as nethserver-ns8-migration-1.1.0-1.ns7.x86_64.rpm |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Scenario
Migration of many NS7 systems with local OpenLDAP account provider to the same NS8 cluster. This scenario is quite common when the administrator want to consolidate multiple small NethVoice installations into a single node.
Problem
The
directory.nhuser domain name can be assigned only once. Currently, a validator prevents the migration of duplicate local OpenLDAP providers. This limitation applies to any application tied to directory.nh, hindering consolidation of multiple services on a single NS8 node.Proposed solution
The LDAP domain will be renamed during the join phase: the user will be asked to enter a valid domain for the new LDAP instance.
The name will be validated on NS8 to avoid naming collisions.
The implementation will be mostly done on NS7 migration tool.
Steps:
Rename the DN in NS7 (e.g., to ldap.domain.com): on NS7 the user will be asked to choose the name of the account provider
Update applications on NS7 to use the new account provider.
Migrate apps and account provider to NS8
When the account provider is migrated, use the user-domain-changed event to notify all applications of the update: applications must connected to new TCP port, also BindDN and BaseDN could change
Make sure that all applications can handle such change. At least the following applications should be reviewed:
ns8-mail (the event user-domain-changed was existing, I just fixed the good property (node vs node_id)
ns8-sogo (added event user-domain-changed)
ns8-roundcubemail (added event user-domain-changed)
ns8-webtop
ns8-ejabberd (the event user-domain-changed was existing, I just fixed the good property (node vs node_id)
ns8-nethvoice (the event user-domain-changed was existing, I just fixed the good property (node vs node_id)
ns8-nextcloud version 1.0.7 (static version for migration) (added event user-domain-changed)
ns8-nextcloud version >= 1.0.8 (added event user-domain-changed)
nethserver-ns8-migration: adapt UI and API to ask and modify the baseDN directory.nh to any other DN like domain.com or sub.domain.com
Refs
The text was updated successfully, but these errors were encountered: